Top tag
Next privilege 500 Rep.
Access review queues
2 10
~16k people reached

  • 0 posts edited
  • 1 helpful flag
  • 4 votes cast
comment Inline functions in C++. What's the point?
Also be aware that not only is the history wrong, but the rules for inline in C99 and later are different from the rules for inline in C++.
comment Filesystem like permissions for C++ type-members
Please give a concrete example of intended usage.
comment How to introduce a computer illiterate 50-year old to programming
@sunday: If he's serious about it, then I'll be happy to help for free, via mail or e.g. facebook chat. or creating a room here on SO if public is OK. Anyway he might start by looking at this tutorial: []. I'm the author of the only tutorial linked to in the C++ FAQ, but that one's old and off-line. He will need a book sooner or later; check out the C++ book list on the SO main site.
comment Is `catch(…) { throw; }` a bad practice?
Nice answer. It could possibly benefit from mentioning that if a compiler that one has to support has a bug in area X, then using functionality from area X is not smart, at least not to use it directly. For example, given the information about the company, I would not be surprised if they used Visual C++ 6.0, which had some sillybugs in this area (like exception object destructors being called twice) -- some smaller descendants of those early bugs have survived to this day, but require careful arrangements to manifest.
comment Strictness in programming methods among Stack Overflow users
On the contrary, the voting on SO tends to present really bad "solutions". Many of them have Undefined Behavior, and many are worst practices. One possible reason is that the person who in general is least competent to select a solution, namely the OP, is the one who has to make such a selection.
comment When would dynamic scoping be useful?
maybe it's easier to implement when the interpreter is implemented in some particular other language?
comment How does compiler handle exceptions that are implicit? Looking for design strategies
@Martin York: it's a construct that ideally would be used to translate exceptions when you're using two or more libraries with non-standard exceptions. It never got into general use, I think mostly because earlier (when such libraries abounded) Visual C++ compilers had a bug that caused exception object's destructor to be called twice for this construct. And nowadays libraries just use standard exceptions, so generally no need. Cheers & hth.,