Elysian Shadows

Okay, after writing a long explanation, I realized how I've been filling your post with something almost unrelated to it. So, I will leave my relevant-to-the-post comment and add a spoiler box on the bottom with my text: The project seems really nice so far. I once implemented a parser for a languag...

I agree on the code comments, you should just comment what really needs comments. I refer to documentation outside the code. I think one example will clarify things: http://www.boost.org/doc/libs/1_49_0/doc/html/chrono.html Of course it doesn't need to be that long and detailed. Sometimes a single d...

On the code organization topic: reading source code should be the last resource when trying to understand how some part of the application works. You (the developer) should supply documentation to guide users (developers using your code, not the end user). I haven't decided yet whether I open sourc...

On the code organization topic: reading source code should be the last resource when trying to understand how some part of the application works. You (the developer) should supply documentation to guide users (developers using your code, not the end user).

Also, I've been told that Visual Studio has the habbit of initializing variables to you, but only on Debug mode (though I can't confirm that, as I don't use it). So, when you compile and run it on Release, some weird events start happening because you forgot to initialize some of them.

Taking all you've said in consideration, I think you should work on an engine. Start with graphics: take some code you already have and make it generic. Develop incrementaly: at each "step", produce something that can be used, even if it's not complete. Then, when you have some of these sm...

Basically what that link is saying, make games first. Make games, and games, and you'll slowly find yourself with more and more re-usable code and be figuring out which things you end up "wanting" to keep that you may normally have noticed you re-write quite often. Not to mention the incr...

That depends on what you want to acomplish. If your goal is to build a game, and what you like to do is game (elements and story) design, and you can get away with the limitations of an engine, you should use one. But if you like the challenge of building an engine, you should go that way. But be wa...

As one of the newest members of the forum (even though more than 20 users signed in since I did, 4 days ago), I'd like to say 'Hello' to everybody. I've discovered you guys a long time ago, when I was just entering college, which was in 2008. I don't remember how, but I found the AIGD series on Yout...