Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

Sup /prog/.

Name: Anonymous 2008-08-10 19:18

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

Name: Anonymous 2008-08-10 20:12

I'd avoid C++/CLI unless you're doing CLR interop, primarily because I don't know of anyone who uses it for anything else, and so it's probably a waste of time unless you'll be doing that.

If you're learning C++/CLI, you're learning a different language (of course, this is blatantly obvious, but it should be said). I would stick to C++, that way you'll learn common C++ idioms and patterns instead of .NET idioms and patterns.

Games are a fun way of learning. I'd stick with 2D (or text-based), and keep it simple to start with, so that you'll actually get used to the language before you really start to use it. If you jump right in with something complex, it's likely you'll want to re-write most of it because you screwed it up, which is just generally a total bummer.

The common first game is pong or breakout, then maybe you could go on to make a geometry wars-style game (or whatever interests you). I'd also start off using existing graphics/audio/etc. libraries such as SDL and Allegro before you go wasting your time writing your own shit.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List