Rasmus Lerdorf wrote:
This comes up once or twice a year. The machine code you compile to is
going to end up looking a lot like the current executor since you don't
have strong types to help you optimize anything. You'd still need to
pass the unions around and do runtime type juggling and all t
Tony Bibbs wrote:
While I could munge the class names in one or more packages as you
suggest then I'm in maintainability hell because when I need to update
one of the other packages (for security, features or bugfixes) you have
to do the name munging again.
C'mon, that ain't right. Next excu
Daniel T. Gorski wrote:
Escpecially due to the new OO features of PHP 5, namespaces are urgently
required for writers of independent libraries which should not clash.
I would claim exactly the opposite.
That's because you already get scoping on names, for free, when you use
objects. The meth
Arnold Daniels wrote:
I see this is the time to do language feature request. So let me add
another. I very often use something like:
/$a = isset($x['abc']) ? //$x['abc'] : null;
/This is to prevent an E_NOTICE from being thrown.
It seems to me like adding a function:
mixed array_get(mixed
