Sup /prog/.

So recently I've begun my age-old quest of actually learning C++.

I've attempted this several times, and like most who give up, stopped after learning the very basics of the language, as I didn't really know where to go from there.

I'm not really looking to be developing specifically for Windows, but I realize that it will be where I do the majority of my work, so does anyone have anything against C++/CLI? If so, why?

Furthermore, what are some ideal "projects" to try to design?
Thanks /prog/,
anon

>>10
That would be J#. Though, granted, C# probably does have more in common with Java than with C++. However, that doesn't really make a difference because Java is just Sun's C++ variant.

>>12
>>13
I don't think "better" or "worst" can be applied like that. Languages are tools and as such which one is "better" heavily depends on what exactly you're trying to achieve. They all have their own advantages and shortcomings. Singling one out is like saying a screwdriver is the "best" (or "worst") tool and that you'd never use a hammer or a wrench (or vice versa). It's nonsense.

>>14
I don't know what I'd call it... never been good with names. But just calling it C++ and hanging on something as a suffix after a slash is obviously misleading. Point and case: the OP.

While it clearly is heavily based on C++ it's still a completely different language. And not just superficially/syntactically... the way it manages memory is completely different. For example, if you try to get the address of a function you won't get its real address... you'll get an address in a jump table that eventually leads to said function. Now that might not make a difference in most cases, but when it does it's a major pain in the ass when you're not expecting it (ie, expecting it to behave like C++ when it's actually not C++ at all).