Re: 5.1.0RC2
| From: | Jessie Hernandez | Date: | Wed, 14 Sep 2005 15:34:45 +0000 |
| Subject: | Re: 5.1.0RC2 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-18910@lists.php.net to get a copy of this message | ||
I agree with Edin. To be consistent, either all interfaces and classes
should be prefixed or none should be prefixed. On the other hand, prefixing
all the old classes/interfaces will cause BC breaks.
<shameless-plug>
This is one case where namespaces are useful. With my namespace patch, all
that would have to be done is to name the class as SPL:Observer. Users can
either implement SPL:Observer or first "import SPL:Observer;" and then
implement Observer.
</shameless-plug>
Regards,
Jessie
"Edin Kadribasic" <edink@emini.dk> wrote in message
news:43283A26.7060000@emini.dk...
> Marcus Boerger wrote:
> > Hello Zeev,
> >
> > i tried to get any feedback from You or andi regarding SPL but none of
you
> > replied so far. Question is whether i should rename some of the new
interfaces
> > and classes to be prefixed by 'Spl'. Also should i drop all constants in
SPL
> > and instead provide class constants whcih we can do right now? Yes i
know
> > that might be BC issue but i'd say it is worth the little break and i am
> > quite sure we shouldn't do it after 5.1 is out. And Last but not least
i'd
> > like to MFH two of the new classes if you don#t mind.
>
> Hm, prefixing "new" interfaces and classes with Spl is the worst thing
> one could do IMHO. Wouldn't it be the best to prefix *all* Spl
> interfaces and classes?
>
> Edin