RE: [PEAR-DEV] PEAR and PHP 5

On Thu, 2003-04-10 at 03:40, Jan Schneider wrote: > 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? No, you're not. The coding standard has to be revised to plan ahead for PHP 5 with namespaces. In its current version the coding standard is geared towards nested classes. - Stig