On 9/4/03 5:55 PM, Lukas Smith wrote:
From: Marcus Börger [mailto:[EMAIL PROTECTED] Sent: Thursday, September 04, 2003 5:13 PM
CS.
PEAR has had their error messages all lowered cased since it's creation. I can only speak for the last 1,5 years were I don’t remember this ever being an issue that was brought up. Maybe something to consider is the fact that in OO you don’t have to have the "ext_" prefix and therefore most method names should only consist of 2 in rare cases 3 words.
I just want to clarify what this means for PEAR. It means we have to change our CS, because otherwise we either have a mixed CS which sort of defeats the purpose or we have to wrap every object that we want to extend that is provided by an extension.
This obviously means a mess beyond believe for PEAR.
I know that there is no way to have studlyCaps being preserved in error messages without a huge performance hit since we have case insensitivity for function/method names. However aside from the other reasons I stated when I initially proposed this, I just wanted to make clear what this means.
So is this really such a huge issue?
Furthermore, ext/dom is already "studlyCapsed", 'cause there it made a lot of sense, since the DOM specs already use studlyCaps...
Just as a remark. I personally do not care much about if studlyCaps or old_school_php_function_names. But I understand PEAR's point and ext/dom with studlyCaps is IMHO the way to go, even if PHP does not care about createDocument or createdocument or crEaTeDoCuMent..
chregu
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
