RE: [PHP-DEV] Re: [PHP-CVS] cvs: php-src / CODING_STANDARDS
| From: | Lukas Smith | Date: | Wed, 03 Dec 2003 15:51:44 +0000 |
| Subject: | RE: [PHP-DEV] Re: [PHP-CVS] cvs: php-src / CODING_STANDARDS | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-6109@lists.php.net to get a copy of this message | ||
> From: Lukas Smith [mailto:smith@backendmedia.com]
> Sent: Wednesday, December 03, 2003 4:46 PM
> > From: Derick Rethans [mailto:derick@php.net]
> > Sent: Wednesday, December 03, 2003 4:46 PM
>
> > On Wed, 3 Dec 2003, Lukas Smith wrote:
> >
> > > > From: Sascha Schumann [mailto:sascha@schumann.cx]
> > > > Sent: Wednesday, December 03, 2003 4:39 PM
> > >
> > > > > The fact that PEAR has a serious problem extending non studlyCap
> > objects
> > > > is
> > > > > probably something a lot of people in PHP core don't care about.
> > > >
> > > > Please elaborate.
> > >
> > > Well if I extend a class that doesnt use studlyCaps, yet the PEAR CS
> > > requires that I use studlyCaps, then I have a problem. Essentially I
> can
> > > only wrap and not extend.
> >
> > Uh? That works just fine...
> >
> >
> > class Foo_Bar extends foo2_bar {
> > }
> >
> > No problem at all.
>
> We are talking about methods names here.
Just to clarify:
Yes there are no technical issues.
There is only the fact that PEAR has decided to have a consistent OO API
based on studlyCaps.
Regards,
Lukas