At 10:19 AM 6/11/2002, Sebastian Bergmann wrote:
>Alex Black wrote:
> >> class foo aggregates bar {
> >> }
> >
> > I think that is a nice solution.
>
> It's not, because it's static. Multiple iheritance is flawed, because
> it's static.
That's hardly considered a flaw almost anywhere, even in
Alex Black wrote:
>> class foo aggregates bar {
>> }
>
> I think that is a nice solution.
It's not, because it's static. Multiple iheritance is flawed, because
it's static.
Have a look at my RfC for delegation:
RfC: http://cvs.php.net/co.php/ZendEngine2/RFCs/004.txt
Further readin
> Hi,
>
> I have promised myself to not get into this discussion for a week now,
> but the smell of dead horse overwhelmed me, so here goes...
heh.
> class foo aggregates bar {
> }
I think that is a nice solution.
> 2. "Optional" strong typing
>
> When people say that being able to do
>
>
> eg: simple db-based shopping cart web site? use PHP... complex internet
> backing system? use Java. Easy!
Use PHP! Easier.
Look, I've built hideously complex things with PHP - commerce systems that
do stream encryption on a per-field basis, complex interconnected process
stuff, large APIs, eve
