Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:6109
Return-Path: <smith@backendmedia.com>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 17313 invoked by uid 1010); 3 Dec 2003 15:53:16 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 17246 invoked from network); 3 Dec 2003 15:53:16 -0000
Received: from unknown (HELO mail.dybnet.de) (195.75.116.242)
  by pb1.pair.com with SMTP; 3 Dec 2003 15:53:16 -0000
Received: (qmail 24840 invoked by uid 508); 3 Dec 2003 15:54:11 -0000
Received: from unknown (HELO vandal) (vandal@212.202.39.121)
  by www.dybnet.de with RC4-MD5 encrypted SMTP; 3 Dec 2003 15:54:11 -0000
To: "'Derick Rethans'" <derick@php.net>
Cc: "'Sascha Schumann'" <sascha@schumann.cx>,
	<internals@lists.php.net>
Date: Wed, 3 Dec 2003 16:51:44 +0100
Organization: BackendMedia GbR
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: 
Thread-Index: AcO5tLncT9hNNf9kR16C6eIMA0mGogAADxtgAAAP+pA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: RE: [PHP-DEV] Re: [PHP-CVS] cvs: php-src / CODING_STANDARDS
From: smith@backendmedia.com ("Lukas Smith")
Message-ID: <php.internals-6109@news.php.net>

> 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