RE: [PHP-DEV] Re: [PHP-CVS] cvs: php-src / CODING_STANDARDS

> From: Hartmut Holzgraefe [mailto:hartmut@php.net] > Sent: Wednesday, December 03, 2003 4:31 PM > Lukas Smith wrote: > >>Pierre-Alain Joye wrote: > >> > >>>And except StudlyCaps is ugly and foo_bar is modern, any realistic > >>>and objective pros to keep foo_bar?.... > >> > >>readability > > > > I dont find it unreadable. > > it is not unreadable but it is definetly *less* readble The funny thing before I started developing in PEAR I wrote very little OO code. And I found the PEAR CS annoying as hell. But now I don't have a problem at all with it. Apparently a bunch of other people don't have a problem with studlyCaps. So much so that they are still using it even in "modern" languages that can handle underscores in method names. So maybe it is just a matter of being used to either form. Now since PHP is developer driven and most of the developers are used to underscores the question is if the fact that a lot of users for OO will be quite used to studlyCaps for OO (actually not using studlyCaps might be confusing to them) matters. The fact that PEAR has a serious problem extending non studlyCap objects is probably something a lot of people in PHP core don't care about. And I guess it shouldn't be THE reason to go either way. But it shouldn't be brushed off totally either. Regards, Lukas