Quote:Original post by MaulingMonkey
He's critisizing the fact that your design makes you feel the need for such prefixes.
Criticizing was not the help I was looking for, but I still don't see the relevance, or why we're thinking that bad design is lurking.
Quote:There's no need to wrap all the members of ParticlePhysics in a namespace scope, because they're allready in a class scope.
...
Why create a bad example when you allready have examples (your previous experiences)?
The method is exactly the same; I'm deriving from a class. The inherited class is very complex, and the base class is very simple. I use the IDE's tools to access and write code, and that means a lot of functions exist for this class that are all thrown together. Compiler auto-completion alone is enough reason to use prefixes. There are about five functions that deal with collision. It would be nice to provide a Collision:: prefix for them in the class. There are at least 15 that work with animations, 6 that update commands, 8 that update command tasks, 13 that handle equipment and armor, five or so that just divide normal updating code, around 12 for AI routines, and 3 for input.
When I type Character->, I get a table of contents. It's great, I would just like to organize it.