What does a C++ intermediate ( In reference to learning ) programmer look like? What are the minimum requirements In terms of knowledge?
>>56088627
hmmm well if it were me, i'd expect you to know more than the basics of the syntax, i'd expect you to know stuff like when/why you make destructors virtual, what constructors you get by default, what diamond inheritance is and what to do about it. basically some of the corner cases, some of the annoying stuff but not all, and not the really in depth stuff. like i wouldnt expect you to know what a kernig lookup is.
i'd also be asking questions like "what do you hate most about the language" cos i'm expecting you to have a thought a bit about it in ways a total n00b generally doesnt.
and also maybe "what do you have to consider when writing threaded code?" or "why are exceptions in c++ a complete abortion and what can you do about it?"
so more than just n00b stuff like "whats a class? what is molyporphism?" but not really really detailed under the hood stuff.
>>56088856
should also add that most places ime dont ask anything like the stuff i mentioned, most places just seem to take you at your word, i've had very few interviews where *they* knew what they were talking about.
>>56088627
difference between stack and heap allocation, pretty good idea of how virtual functions work, some experience with templates
>>56088627
I'd argue that you can't be an intermediate programmer with respect to a language. The kind of knowledge that makes a programmer intermediate is much more abstract than the rules of one specific language.
printing hello world with cout rather than printf