StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Migration? I thought WG21 fought hard to preserve all the compatibility. Unless you used export you do not need migration, existing code is fine. </p> <p>I guess you really meant the question for refactoring the existing code to pick up C++11 features. Here I'd apply the general wisdom about refactoring -- never do it without a proper goal and value-based motivation. </p> <p>Just that new shiny features got introduced does not impose technological debt on your code. </p> <p>I suggest you start using new features in new code, and apply more liberal changes it where you refactor for different reasons anyway. And start thinking in general reshape only when having multiple styles is considered a real pain. (The multi-paradigm nature of C++ normally should allow quite much freedom, and force uniform approach only occasionally.)</p> <p>From the new features what I'd focus on:</p> <ul> <li>auto. All my new code is full of <code>auto const</code> and <code>auto const&</code> locals omitting the types. Ok, one suggested globalreplace contradicting what I said previously: replace ::iterator usage by auto if you have for loops using them.</li> <li>lambdas, if you use algos with one-shot functions</li> <li>the new threading stuff, especially <code>std::future</code> if applies to the project</li> </ul> <p>If you happen to use 'std::auto_ptr' probably a good candidate for globalreplace too.</p> <p>I left out move semantics because I'm yet to jump on them, not sure of the impact, so I leave it for others to suggest or not.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload