RE: [PEAR-DEV] PEAR and PHP 5
| From: | Stig S. Bakken | Date: | Thu, 10 Apr 2003 20:19:40 +0000 |
| Subject: | RE: [PEAR-DEV] PEAR and PHP 5 | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-15106@lists.php.net to get a copy of this message | ||
On Thu, 2003-04-10 at 14:33, Jan Schneider wrote:
> Quoting "Stig S. Bakken" <ssb@fast.no>:
>
> > On Thu, 2003-04-10 at 03:40, Jan Schneider wrote:
> > > 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.
>
> But isn't that the opposite of the
> automagically-convert-packages-to-php5-namespaces-approach?
Not really. This problem is caused by the fact that we "lost" nested
classes as a ZE2 feature, but the PEAR CS was build for it. The reason
we ended up with nested classes in the first place PEAR CS issues, and
wanting to avoid symbols such as Foo_Bar::Bar (but rather Foo::Bar).
You could say that basing the PEAR CS on the future bringing nested
classes (or something with the same effect) was a calculated risk. :-P
> And how do you want to handle the need of having both (php4 and php5)
> versions of a package? Some applications may already use the namespace
> syntax, other still depend on the old one. But both may need the same pear
> package?
You mean php4 and php5 versions of the _same_ package? I definitely
don't have all the solutions here, but I guess that could be solved with
two install trees. Feel free to bring up examples that we can use to
define the problem better.
- Stig