[Is this the right news?]
Recently I downloaded PHP 5.0.0 and read the RFCs, I sadly noticed that a
Namespace proposal was declined. Why? I've been using PHP for many years and
I've found problems when trying to "glue" several third parties codes.
PEAR has come with a not-quite-nice solution to t
Please read the archives!
Zeev
At 18:55 15/08/2004, Manuel Vázquez Acosta wrote:
[Is this the right news?]
Recently I downloaded PHP 5.0.0 and read the RFCs, I sadly noticed that a
Namespace proposal was declined. Why? I've been using PHP for many years and
I've found problems when trying to "glue"
Zeev,
I too have been searching the archives for subjects on 'namespace' and found
allot of back and forth opinions on it but not a real summary about its
conclusion. Basically, I have allot of code at work still in php4 that that
uses it own class importing mechanism than just include|require[_on
Hello Justin,
Monday, August 16, 2004, 4:08:46 PM, you wrote:
> Zeev,
> I too have been searching the archives for subjects on 'namespace' and found
> allot of back and forth opinions on it but not a real summary about its
> conclusion. Basically, I have allot of code at work still in php4 that
Thanks.
I figured as much but when I implemented this the terms 'Namespace' and
'import' just sounded so sexy to me.
-Justin
"Marcus Boerger" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hello Justin,
>
> Monday, August 16, 2004, 4:08:46 PM, you wrote:
>
> > Zeev,
>
> > I too ha
> There's a good chance that later PHP versions (maybe 5.2 or 6 or whatever)
> have something like namespaces or packages which require at least the
> keyword 'import'. That's an example for the reason i never use names that
> are used as keywords in other languages.
>
That sounds like good news!
At 21:06 16/08/2004, Marcus Boerger wrote:
Hello Justin,
Monday, August 16, 2004, 4:08:46 PM, you wrote:
> Zeev,
> I too have been searching the archives for subjects on 'namespace' and
found
> allot of back and forth opinions on it but not a real summary about its
> conclusion. Basically, I have
> I don't see how it could change in the future, but that's
> just my 2c :)
Thanks, thats all I was really looking for. The status of the terms, cause
if they're not being reserved then I would like to continue using them -- at
my own risk. As Marcus points out, its might not be the best idea to
i
I would just like to echo some concerns on namespaces. I've pioneered
the adoption of PHP in some enterprise development groups at Avaya, and
it's been adopted on the merits of the fastest and easiest tool for web
interface development.
Every now and then someone duplicates a class name and mutte
