"That doesn't make sense. A feature can not be both primitive and advanced. And the proper way to learn in C++ is to start by using the very robust features of the Standard Library, expanding to lower-level functionality as needed."

no, perhaps let me give you examples (in C++)

primative: built in types (int, char), built in meta types (function, array), control constructs (if statements). Essentially primatives are what the compiler handles
nonprimative: the standard library, your own code. Essentially stuff that is implemented.

beginner: stuff that beginners should start with
advanced: things with complications

so for example the int type is primative (handled by the compiler) and beginner level (suitable for beginners). Arrays are primative (handled by the compiler) but are advanced (beginners should use string and vector instead)

"You realize that the compiler can not determine the error in your example?"

yes, and that is exactly the kind of error that causes me the most trouble. C++ cannot catch a typographical error in a string. It can catch other types of typographical errors. Languages without compile-time type checking are able to catch fewer typographical errors at compile-time. Python is such a language. This concept can be extended. I was working on Python once and using a poorly documented API. It took me a while to realize that the function that I was calling was returning a tuple of types a and b rather than just b. If it were checked at compile-time I would have gotten an error message along the lines of:

Error # 3495734975 on line 63: cannot convert a,b to a

which would have immediately alerted me to the problem. Furthermore if you don't know what the error message is you can pop it into your help files or google, or post the error message on GameDev.

"*yawn* Collegiate example. C'mon... impress me!"

well... if you must know I am making it because I am dissatisfied with C++... but I still like C++ far better than Python or any other language.