reflection api -> camelcaps

22 years ago by George Schlossnagle — view source — reply

unread

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

22 years ago by Marcus Boerger — view source — reply

unread

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

22 years ago by Derick Rethans — view source — reply

unread

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

22 years ago by George Schlossnagle — view source — reply

unread

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

22 years ago by Derick Rethans — view source — reply

unread

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

22 years ago by Sebastian Bergmann — view source — reply

unread

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/

22 years ago by George Schlossnagle — view source — reply

unread

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?

Well, as the classes are builtin's it's not so clear to me that the
packag naming rules apply directly. But this is a sound objection.

George

22 years ago by Adam Maccabee Trachtenberg — view source — reply

unread

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?

Well, as the classes are builtin's it's not so clear to me that the
packag naming rules apply directly. But this is a sound objection.

This raises my question of my the new Exception class uses CamelCaps instead
of underscores?

For instance, its methods are: getMessage(), getCode(), etc.

I don't think any other built-in method or packaged extension does this.

-adam

--
adam@trachtenberg.com

22 years ago by George Schlossnagle — view source — reply

unread

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?

Well, as the classes are builtin's it's not so clear to me that the
packag naming rules apply directly. But this is a sound objection.

This raises my question of my the new Exception class uses CamelCaps
instead
of underscores?

For instance, its methods are: getMessage(), getCode(), etc.

I don't think any other built-in method or packaged extension does
this.

I've been re-pointed to CODING_STANDARDS, which changed since last I
looked. Classnames get underscores, method names get camelcaps.

George

22 years ago by Christian Stocker — view source — reply

unread

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?

Well, as the classes are builtin's it's not so clear to me that the
packag naming rules apply directly. But this is a sound objection.

This raises my question of my the new Exception class uses CamelCaps instead
of underscores?

For instance, its methods are: getMessage(), getCode(), etc.

I don't think any other built-in method or packaged extension does this.

ext/dom and ext/xsl use camelCaps as well

chregu

-adam

22 years ago by Derick Rethans — view source — reply

unread

This raises my question of my the new Exception class uses CamelCaps instead
of underscores?

For instance, its methods are: getMessage(), getCode(), etc.

I don't think any other built-in method or packaged extension does this.

ext/dom and ext/xsl use camelCaps as well

here it makes a bit sense because it's the Dom standard to do so and to
have the possibility to point at the dom docs instead of forcing the
developers to write documentation ;-)

Derick

reflection api -> camelcaps View as Markdown