Why does not everybody consider the existent facts, and not what one likes and other does not like?
It would be more logical. The facts: - There are already extensions that use studlyCaps(DOM, mysqli, and others), and probably WONT change. - In the future, probably several other external OO extensions will use studlyCaps. - Pear and other frameworks are using studlyCaps. - Almost all external technology wich PHP will interact now or in the near future uses studlyCaps. Why doesn´t make that a STANDARD for OO code so????? The only thing you will get if decide to use underscores, is that there will be a CS with several exceptions. Like somethings that use studlycaps and others that use underscores. And never will have a consistent Coding Standards. By the other side, adopt studlycaps for OO code will avoid all these problems and create a clear CS that CAN BE FOLLOWED (we know that adopting underscores will generate several exceptions). I think these are the facts to think about. I personaly, prefer underscores, but I think in this case studlyCaps should be used for OO code. And just because with it, is possible to create a consistent CS with no exceptions. Thanks, Eduardo R. Maciel __________________________________ Do you Yahoo!? Free Pop-Up Blocker - Get it now http://companion.yahoo.com/ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
