The problem is this creates a difference with the PEAR classes and PEAR
standards.
I agree that on the whole using underscores is a better method, its my
preference as well. But PEAR already made the decision to go with
studlyCaps, and we should follow in suite (as they are the largest
collection
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
Related articles:
http://marc.theaimsgroup.com/?l=php-dev&m=10527308470&w=2
http://marc.theaimsgroup.com/?l=php-dev&m=104837776401767&w=2
Moriyoshi
[EMAIL PROTECTED] (Marcus Börger) wrote:
> Hello internals,
>
> referring to paragraph 6 of our CODING_STYLES i changed my own spl extension
>
> From: Marcus Börger [mailto:[EMAIL PROTECTED]
> Sent: Thursday, September 04, 2003 5:13 PM
> referring to paragraph 6 of our CODING_STYLES i changed my own spl
> extension
> and parts of SQLite which interact with spl.
>
> [6] Method names follow the 'studlyCaps' (also referred to as 'bumpy
ca
On Thu, 4 Sep 2003, Marcus Börger wrote:
> As the only consequence i think we should remove that part 6 from our CS.
let's replace it with this:
[6] Method names follow the same naming style as normal
functions like "mysql_connect".
Good:
'connect()'
'get_data()'
'buil
> As the only consequence i think we should remove that part 6 from our CS.
Certainly. I did not even know it was there.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
Hello internals,
referring to paragraph 6 of our CODING_STYLES i changed my own spl extension
and parts of SQLite which interact with spl.
[6] Method names follow the 'studlyCaps' (also referred to as 'bumpy case'
or 'camel caps') naming convention, with care taken to minimize the
letter
