On Fri, Mar 26, 2004 at 09:53:28AM -0500, George Schlossnagle wrote: > As Edin and Lukas have both pointed out, one of the major precepts of > OO programming is that you can (and often do) overload methods in your > parent. Adopting two different styles really doesn't work if you ever > want to use any of the in-core classes, as it will force your own code > to adopt both notions. In fact, the argument that people use > StudlyCaps in their own code is precisely why it should be adopted in > OO code, so that overloading won't result in a mishmash of styles.
You'll have that mishmash of styles anyway if you use camel case naming, since the vast majority of existing functions doesn't use it. I don't see that 'being able to distinguish between built-in and user-defined' thing as valid either, but if you want real consistency you'd go and make everything conform to ONE naming standard. There's no reason that methods should be different from functions at all. In a way, functions are just methods with PHP as the implicit reciever... Oh, and the strpos/str_repeat inconsistency should be 'fixed' too, maybe make strpos an alias to str_pos or alike... -- Regards, Stefan Walk <[EMAIL PROTECTED]> -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
