reflection api -> camelcaps

php.internals

George Schlossnagle

22 years ago
I'd like to convert the reflection API to the current php standard of CamelCaps (instead of underscores) for it's class and method names. Any objections? George

Marcus Börger

22 years ago
Hello George, Tuesday, December 2, 2003, 6:58:58 PM, you wrote:
> I'd like to convert the reflection API to the current php standard of > CamelCaps (instead of underscores) for it's class and method names. > Any objections?
No objections. Strong agreement.'
-- Best regards, Marcus mailto:helly@php.net

Derick Rethans

22 years ago
On Tue, 2 Dec 2003, George Schlossnagle wrote:
> I'd like to convert the reflection API to the current php standard of > CamelCaps (instead of underscores) for it's class and method names. > Any objections?
yes Derick

George Schlossnagle

22 years ago
On Dec 2, 2003, at 1:18 PM, Derick Rethans wrote:
> On Tue, 2 Dec 2003, George Schlossnagle wrote: > >> I'd like to convert the reflection API to the current php standard of >> CamelCaps (instead of underscores) for it's class and method names. >> Any objections? > > yes
Care to elaborate? George

Derick Rethans

22 years ago
On Tue, 2 Dec 2003, George Schlossnagle wrote:
> > On Dec 2, 2003, at 1:18 PM, Derick Rethans wrote: > > > On Tue, 2 Dec 2003, George Schlossnagle wrote: > > > >> I'd like to convert the reflection API to the current php standard of > >> CamelCaps (instead of underscores) for it's class and method names. > >> Any objections? > > > > yes > > Care to elaborate?
Sure, i'll repeat what I said on IRC: 19:47 <@Derick> 1. it's not any standard 19:47 <@Derick> 2. it's ugly as hell 19:47 <@Derick> (it was 'standard' for a while but due to popluair demand we removed it from coding_standards) 19:57 <[GeorgeS]> Derick: didn't see the change to CODING_STANDARDS. But that's a good reason. Please have a look at the archives for this, as I remember having a discussion about this too. IMO all internal functions use the underscore way, so why deviate for methods? (This is as far as I go, no need to discuss this again) Derick

Lukas Smith

22 years ago
> From: Derick Rethans [mailto:derick@php.net] > Sent: Tuesday, December 02, 2003 8:02 PM
> On Tue, 2 Dec 2003, George Schlossnagle wrote: > > > > > On Dec 2, 2003, at 1:18 PM, Derick Rethans wrote: > > > > > On Tue, 2 Dec 2003, George Schlossnagle wrote: > > > > > >> I'd like to convert the reflection API to the current php standard of > > >> CamelCaps (instead of underscores) for it's class and method names. > > >> Any objections? > > > > > > yes > > > > Care to elaborate? > > Sure, i'll repeat what I said on IRC: > 19:47 <@Derick> 1. it's not any standard > 19:47 <@Derick> 2. it's ugly as hell > 19:47 <@Derick> (it was 'standard' for a while but due to popluair demand > we > removed it from coding_standards) > 19:57 <[GeorgeS]> Derick: didn't see the change to CODING_STANDARDS. > But that's a good reason. > > Please have a look at the archives for this, as I remember having a > discussion about this too. IMO all internal functions use the underscore > way, so why deviate for methods? (This is as far as I go, no need to > discuss this again)
There was an argument raised by Marcus a while back. The main point was that PHP's lack of preserving of case would be a major draw back to studlyCaps. However since he solved the issue the discussion faded away (for obvious reasons). Regards, Lukas

Sebastian Bergmann

22 years ago
George Schlossnagle wrote:
> I'd like to convert the reflection API to the current php standard of > CamelCaps (instead of underscores) for it's class and method names.
Why deviate from PEAR CS in this?
-- Sebastian Bergmann http://sebastian-bergmann.de/ http://phpOpenTracker.de/ Das Buch zu PHP 5: http://professionelle-softwareentwicklung-mit-php5.de/