c++ Programming Glossary: risky
Why is modulo operator necessary? http://stackoverflow.com/questions/10097534/why-is-modulo-operator-necessary solution. The software solution is less painful costly risky. Now I assume your question is not what the winning poster answered...
In C++, why use static_cast<int>(x) instead of (int)x? http://stackoverflow.com/questions/103512/in-c-why-use-static-castintx-instead-of-intx that makes it possible. The only time it's a bit risky is when you cast down to an inherited class you must make sure..
Problem with Macros http://stackoverflow.com/questions/1351051/problem-with-macros while defining macros #define SQUARE X X X is a bit less risky. Ian Kemp wrote it first in his comment You could instead use..
Dynamically allocating an array of objects http://stackoverflow.com/questions/255612/dynamically-allocating-an-array-of-objects Note Doing any operation on src after a move is risky apart from destroy until you put it into a specific state...
C++ - passing references to boost::shared_ptr http://stackoverflow.com/questions/327573/c-passing-references-to-boostshared-ptr bit of advice that applies here don't bother making risky changes to your code for the sake of performance until you've..
Qt applications on new Mac App Store http://stackoverflow.com/questions/4337855/qt-applications-on-new-mac-app-store no theming and cannot use private APIs. Still seems like a risky proposition over pure ObjC. Anyone else tempted c osx qt app..
How to implement the factory pattern in C++ correctly http://stackoverflow.com/questions/5120768/how-to-implement-the-factory-pattern-in-c-correctly in C . So if Foo is expensive to copy this approach is risky. And what if Foo is not copiable at all Well doh. Conclusion..
Why should `new` be used as little as possible? http://stackoverflow.com/questions/6500313/why-should-new-be-used-as-little-as-possible not be neccessary delete mString Is actually a lot more risky to use than the following one class Line public Line std string..
How to put different template types into one vector http://stackoverflow.com/questions/696399/how-to-put-different-template-types-into-one-vector and use pointers to that class. Note that this option is risky in terms of memory management. You might want to make it safer..
C++ char* vs std::string [closed] http://stackoverflow.com/questions/801209/c-char-vs-stdstring speed is crucial and you're willing to accept some of a risky business because of the memory management. Are there other scenarios..
|