On Sat, 2003-03-22 at 21:14, Marcus Börger wrote:
> At 00:43 23.03.2003, Sterling Hughes wrote:
> >On Sat, 2003-03-22 at 19:02, Moriyoshi Koizumi wrote:
> > > Hi,
> > >
> > > As per naming convention, I think it'd be nice if the methods were
> > > named as:
> > >
> > > getmessage => get_message
> > > getcode => get_code
> > >
> > > If those are corrected, +1 for this feature.
> > >
> >
> >I was thinking of that - I would personally prefer get_message() and
> >get_code() naming, but that goes against pear's naming conventions, and
> >I want this to integrate well with pear (as a base class.)
>
>
> I agree with moriyoshi here. If pear has a problem with that - than please
> change
> pear and do not add more inconsistent featrures instead. The exception class
> itself was not only once requested.
>
Well, Moriyoshi agreed with me, once he understood the rationale. So,
its only you. :)
As for inconsistency, PEAR is the standard for OO php code, and
studlyCaps are a part of their standards. PHP standards exist for
procedural code, which is a different beast.
> Another point however is the function name zend_register_default_interfaces()
> in the C code. Since we have interfaces and you do not register an
> interface with
> that function you are missleading here so please name that function something
> like zend_register_default_exceptions() and change the filenames to contain the
> word exception instead of interfaces.
>
No, you misunderstand the purpose. The idea of this file is to add any
standard classes, interfaces, etc. Exception just happens to be the
first practical example.
-Sterling
> regards
> marcus
--
"Reductionists like to take things apart. The rest of us are
just trying to get it together."
- Larry Wall, Programming Perl, 3rd Edition
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
