i'll try to answer both Marcus and Wez here:
> Where is the big difference (first is postfix syntax, second is prefix syntax).
the difference is between whether you have to change *lots* of existing code
or do exactly *one* cast in new code while you write it:
$timer = (Timer) $MI_obj;
librar
> If you want to access an aggregated object directly you can do:
> $obj->Timer->method();
well, that's exactly what shouldn't be done and what polymorphism
is trying to eliminate... consider a huge code library which operates
on an object of class Timer and that we want to reuse this library.
n
some thoughts concerning member name collisions:
(i will also demonstrate a common shortcoming that i personally
consider a design flaw that exists both in C++ and in Java - it sure
would be good to avoid the same flaw in PHP - even if MI doesn't
get into ZE2, keep this in mind for the future
hi all,
> I'm personally in favour of having MI in PHP, with the serious alternative
> being interfaces. I have failed to understand what interfaces would mean
> in a language such as PHP, though, while I can see the clear hands-on use
> for MI.
1) the whole concept of interfaces as they ar
hi,
has anybody ever thought about supporting HTML 4.01 in
the DOMXML extension as Gnome libxml supports it anyway?
should be a relatively simple addon, yet extremely useful for
processing layout templates and finally killing the long thread
of discussion on the brain-dead text-substituting tem
