Reading the comments there reminds me of people who said that if you aren't using camel case you're actively boycotting other programmers by making identifiers less readable... I actually find all lowercase to be more readable than camel case (although if you use all lowercase then you must use underscores, otherwise yes, it's an unreadable mess).
Which reminds me, with my current style things go like this:
- Identifiers: lowercase
- Custom types: camel case
- Constants: uppercase
How would it be with camel case for identifiers? Like this? (going by the Windows API, which does exactly this)
- Identifiers: camel case
- Custom types: uppercase
- Constants: uppercase
Yeah, not hard to see the issue there, constants and types look the same under that convention. Sure, somebody will argue that smart syntax highlighting should take care of that, but you don't always have that available, and you shouldn't rely on it being available either, especially if you're going to be sharing the code (and you should program like you will!).
