RE: [PEAR-DEV] PEAR and PHP 5
| From: | Jan Schneider | Date: | Thu, 10 Apr 2003 01:40:04 +0000 |
| Subject: | RE: [PEAR-DEV] PEAR and PHP 5 | ||
| References: | 1 2 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-15084@lists.php.net to get a copy of this message | ||
Quoting "Stig S. Bakken" <ssb@fast.no>:
> On Wed, 2003-04-09 at 17:12, Lukas Smith wrote:
> > > From: George Schlossnagle [mailto:george@omniti.com]
> > > Sent: Wednesday, April 09, 2003 4:47 PM
> >
> > > On Wednesday, April 9, 2003, at 10:29 AM, Sebastian Bergmann wrote:
> > >
> > > > Stig S. Bakken wrote:
> > > >> What we could do is to always bundle ext/tokenizer in PHP 5 and
> > > >> re-format symbols in PHP 4 PEAR code during install.
> > > >
> > > > ext/tokenizer is already bundled and enabled by default.
> > >
> > > Doesn't this seem like it could cause a maintenance nightmare in that
> > > any problems with the munging operation would leave many people with
> > > borked or partially borked PEAR installs?
> >
> > Good point.
> > Maybe the munging needs to happen on pear.php.net then.
> > This would allow us to more easily spot the problems and fit it.
> > So basically the pear installer would request the file for php5, php4,
> > phpX.
> >
> > If the files haven't been "munged" they get munged and stored on the
> > server for future requests.
>
> This is a good point. So translation should be done during upload
> instead.
I didn't take a closer look at namespaces yet, but don't you have to provide
the namespace if you call classes/function inside them?
That means that not only the classes themselves have to be rewritten but
also all calls to these classes in other pear packages that depend on them.
Or am I completely on the wrong track?
Jan.
--
http://www.horde.org - The Horde Project
http://www.ammma.de - discover your knowledge
http://www.tip4all.de - Deine private Tippgemeinschaft