It is a matter of judgment. I will typically let std::swap do the job for prototyping code, but for release code write a custom swap. I can usually write a custom swap that is about twice as fast as 1 move construction + 2 move assignments + 1 resourceless destruction. However one may want to … Read more
Support for <iframe> is still there in HTML 5, so I don’t think this will change in the near future. To answer your other questions: <iframe>s (as frames in general) are most of the time not user-friendly: They don’t allow easy access of the content in the frame via an URL (without losing the content … Read more
I think it should be considered effectively obsolete for new code, but there’s no compelling reason to mark it obsolete and create warnings in all code which was written before 2.0 was released. In my experience, most of the types and members which have been marked obsolete by Microsoft are actively dangerous in some respect, … Read more
Deprecated Functions Insecure A perfect example of such a function is gets(), because there is no way to tell it how big the destination buffer is. Consequently, any program that reads input using gets() has a buffer overflow vulnerability. For similar reasons, one should use strncpy() in place of strcpy() and strncat() in place of … Read more
Vector synchronizes on each individual operation. That’s almost never what you want to do. Generally you want to synchronize a whole sequence of operations. Synchronizing individual operations is both less safe (if you iterate over a Vector, for instance, you still need to take out a lock to avoid anyone else changing the collection at … Read more