useful - Page 102 - Developer IT

Using YUI with Spring framework

- by sword101

hey guys i am new to ajax technology and i want to use YUI technology with spring framework so please guide me where to start;useful links & tutorials thank you.

Some clarification on rvalue references

First: where are std::move and std::forward defined? I know what they do, but I can't find proof that any standard header is required to include them. In gcc44 sometimes std::move is available, and sometimes its not, so a definitive include directive would be useful. When implementing move semantics, the source is presumably left in an undefined state. Should this state necessarily be a valid state for the object? Obviously, you need to be able to call the object's destructor, and be able to assign to it by whatever means the class exposes. But should other operations be valid? I suppose what I'm asking is, if your class guarantees certain invariants, should you strive to enforce those invariants when the user has said they don't care about them anymore? Next: when you don't care about move semantics, are there any limitations that would cause a non-const reference to be preferred over an rvalue reference when dealing with function parameters? void function(T&); over void function(T&&); From a caller's perspective, being able to pass functions temporary values is occasionally useful, so it seems as though one should grant that option whenever it is feasible to do so. And rvalue references are themselves lvalues, so you can't inadvertently call a move-constructor instead of a copy-constructor, or something like that. I don't see a downside, but I'm sure there is one. Which brings me to my final question. You still can not bind temporaries to non-const references. But you can bind them to non-const rvalue references. And you can then pass along that reference as a non-const reference in another function. void function1(int& r) { r++; } void function2(int&& r) { function1(r); } int main() { function1(5); //bad function2(5); //good } Besides the fact that it doesn't do anything, is there anything wrong with that code? My gut says of course not, since changing rvalue references is kind of the whole point to their existence. And if the passed value is legitimately const, the compiler will catch it and yell at you. But by all appearances, this is a runaround of a mechanism that was presumably put in place for a reason, so I'd just like confirmation that I'm not doing anything foolish.

Search Results

Search found 7338 results on 294 pages for 'useful'.

Page 102/294 | < Previous Page | 98 99 100 101 102 103 104 105 106 107 108 109 | Next Page >

- by sword101

- by Dennis Zickefoose

- by paracaudex

- by philip

- by theycallmemorty

- by Adam Paynter

- by fang

- by James P.

- by yodaj007

- by Romias

- by qichuan

- by Algorist

- by credford

- by Ben Aston

- by fengshaun

- by James

- by Jangwenyi

- by harigm

- by moon

- by anon

- by Sam152

- by boomhauer

- by Teifion

- by HotTester

- by Ravisha

< Previous Page | 98 99 100 101 102 103 104 105 106 107 108 109 | Next Page >