However, I too can point out the example of inconsistant naming conventions.

You are right. I overlooked a few, and I will fix them when I upload the next site-update. Thanks.

game_state was from the old article, however, the function naming convention is not inconsistent.

I use lowercaseCapsCapsCaps () instead of CapsCapsCaps for functions.

the Allegro functions are then easily seperated from mine because Allegro uses lower_lower () format.

I didn't want to use CapsCaps () for functions and variables, because it can be confusing for a newbie.

I am going to write up a naming convention document so that readers can quickly understand why I do things the way I do them.

No one is perfect. I'm not claiming that my way is perfect, its just I have my style. No one is forcing anyone to use it. Just accept that it is MY style._________________Principal Software Architect
Rambling Indie Games, LLC

Everyone seems to complain about style these days. Let me take a look at the coding style of these whiners...I will poke many holes in their coding style, citing reference after reference to why their style is inferior to the professionals. Before one whines about style, maybe they should take a look at their own and make some "corrections"...or maybe they should just leave a person's individual coding style the hell alone and whine about something else worth whining about (or perhaps stop whining altogether, since whining accomplishes NOTHING!)._________________If you play a Microsoft CD backwards you can hear demonic voices. The scary part is that if you play it forwards it installs Windows. - wallace

Everyone seems to complain about style these days. Let me take a look at the coding style of these whiners...I will poke many holes in their coding style, citing reference after reference to why their style is inferior to the professionals. Before one whines about style, maybe they should take a look at their own and make some "corrections"...or maybe they should just leave a person's individual coding style the hell alone and whine about something else worth whining about (or perhaps stop whining altogether, since whining accomplishes NOTHING!).

Those "other people" are going to vary though. No one's code can be read and understood by everyone. For example: People have been parroting for ages about how great the NeHe tutorials are, but I can't make heads or tails of that crap, and I don't exactly think I'm an idiot or inconsequential. Great style? Completely open to interpretation. Furthermore, when working on a team, obviously you have to have some accepted standards, but when working on your own stuff, the only person who needs to understand it is you yourself. There are a few norms that everyone should probably follow to make their own code more readable to even themselves that in no way hinders the effectiveness of the compiler (using things such as int iVariableName is VERY effective), but beyond that, coding style is fair game._________________If you play a Microsoft CD backwards you can hear demonic voices. The scary part is that if you play it forwards it installs Windows. - wallace

Those "other people" are going to vary though. No one's code can be read and understood by everyone. For example: People have been parroting for ages about how great the NeHe tutorials are, but I can't make heads or tails of that crap, and I don't exactly think I'm an idiot or inconsequential. Great style? Completely open to interpretation. Furthermore, when working on a team, obviously you have to have some accepted standards, but when working on your own stuff, the only person who needs to understand it is you yourself. There are a few norms that everyone should probably follow to make their own code more readable to even themselves that in no way hinders the effectiveness of the compiler (using things such as int iVariableName is VERY effective), but beyond that, coding style is fair game.

qft. I don't understand why DeveloperX is receiving so much criticism about this. The articles are for total noobs and as long as they understand it, who cares. And, if you're so great at coding, then write one up yourself.

white_wolf, are you completely airheaded? I was DEFENDING DevX, not criticizing him. Get a clue!_________________If you play a Microsoft CD backwards you can hear demonic voices. The scary part is that if you play it forwards it installs Windows. - wallace

Eww, Hungarian Notation! I personally find that to be the single most ugly thing ever. Modern editors usually have discovery techniques which make it quite old. Good languages, conversely, would hardly be agile if it were used.

I do agree with the consistency thing, too. For any who care, my criticism earlier in this thread had nothing to do with the coding style of DeveloperX's code; I just don't think his abstraction is usable, even for a neophyte. A properly written abstraction should make code easier to read, not obscure it behind a bunch of meaningless, inconsistent cruft._________________"...LeoDraco is a pompus git..." -- Mandrake

[
qft. I don't understand why DeveloperX is receiving so much criticism about this. The articles are for total noobs and as long as they understand it, who cares. And, if you're so great at coding, then write one up yourself.

Nod has always been there defending me man, any input he has on anything is always appreciated.I think you may have misread his post, if you felt that he was 'against' me.

And, Nod, please lighten up on the wolf. ;) He's new, and I don't want him to feel the way I used to back when I had started here.

LeoDraco:
I use Hungarian notation when I work on a large project with others, because it makes it easier to quickly glance at, and understand the code. I tend to use my own subsets of it though, and as such I do make sure that I provide a 'legend' for the coding standard that was used. Sure, it IS ugly, but who said code had to be pretty? ;)

Also, I may not have said this before, but if you want to write an article that 'properly' (to you) uses an abstraction then please, by all means go ahead. I'll stick it on my site, with your name on it._________________Principal Software Architect
Rambling Indie Games, LLC

Far be it for a developer who has to look at code all day to desire the code to read well and look pretty.

"Pretty" code writes faster; there are less special cases that need to be remembered and maintained. As a developer, writing code quickly is a good goal to aim toward; anything that hinders that should be deprecated, and anything that promotes that should be lauded._________________"...LeoDraco is a pompus git..." -- Mandrake

Acutally, I was trying pointing out that DebugBox() and initializeGameEngine() were inconsistant because DebugBox() uses the CapCapCap() style whereas initializeGameEngine() uses lowerCapCap() style. Since you have established to use lowerCapCap() style, then it would make more sense to lowercase the "d" in DebugBox() as in debugBox().

Quote:

I didn't want to use CapsCaps () for functions and variables, because it can be confusing for a newbie.

definitely not! Usually most people define a different style for functions, variables and constants. This is definitely a good way to go!

Acutally, I was trying pointing out that DebugBox() and initializeGameEngine() were inconsistant because DebugBox() uses the CapCapCap() style whereas initializeGameEngine() uses lowerCapCap() style. Since you have established to use lowerCapCap() style, then it would make more sense to lowercase the "d" in DebugBox() as in debugBox().

And, Nod, please lighten up on the wolf. ;) He's new, and I don't want him to feel the way I used to back when I had started here.

No problem, I'll be nice to the wolfie. :D_________________If you play a Microsoft CD backwards you can hear demonic voices. The scary part is that if you play it forwards it installs Windows. - wallace