|I'm glad I never learned from you. |
Incidentally, I am very glad that I am not a college professor, as I lack the needed patience.
In the vast majority of American universities that I have researched, C++ is not an entry level class. Prior topics usually involve a type of introduction to computer programming most often using pseudo-code. The concepts of variables, control structures, memory theory, etc should already have been mastered in a language-agnostic fashion prior to taking a C++ course. Learning the syntax of the various facets of C++ is very important and should most definitely take longer than a single session, being taught in the correct order
. From my experience, these topics that are glazed over the first time around almost always end up coming back to haunt the student later on in their career. What's worse? The students are usually given no indication that what they've been taught is considered to be bad practice
Having a 2^32 character long string is absurd, and there is certainly no "practical conflict" in most cases. That's quite a bad example for me to be nitpicking, but that was on the first hit
that I got when I searched google for a college C++ course. That is nothing compared to the greater horrors that are being taught even as I type this.
|Is he wrong? Technically, but in what possible scenario would him giving the "correct" answer not simply confuse students in their first C++ class?|
Shouldn't it be the professor's responsibility to make sure that the students are actually absorbing the material rather than standing at the podium and reading verbatim from a text-book? It seems to me that any professor that just glazes over material, dumbing it down enough so there is no confusion, is taking the easy way out and frankly is not doing their job. Conversely, the students that aren't willing to devote the time to conquer their confusion need to reevaluate what they are going to school for.
I'm extreme, I know and accept that.
On a trailing note, I just hate the signedness comparison warnings that many people just ignore (or aren't aware of) and leave in their code. If only that college professor had hit that home...
Ah...just remembered another thing:
|Do you really EVER expect to have a string with a size of 4294967295?|
A std::string (size_t = unsigned 32 bit integer) with that size would already be broken, as it would have a length of std::string::npos.