[KLUG Programming] Subtley *NASTY* PHP4/5 Difference

[Adam Tauno Williams]

> >> a switch that disposes of objects based upon their type (pretty
> >> common I suppose)
> >I thought being able to avoid exactly that was the major selling
> >point of object-oriented code.  Why can't each class know how to
> >dispose of its own objects?
> A destructor can be defined... 

Theoretically, but not in PHP4.

And, sorry, by dispose I didn't mean destroy.  Is serialization
destruction of the origin class?  This part seems a little vague to me.
The class is later 'resurrected' then.

> I don't remember what PHP3 did.. anyone out there who does, please
> don't be shy!

PHP3 was a bloody mess that just kind of sneered at the concept of
"class".  PHP4 is better, PHP5 is supposedly much better, but I haven't
dug in much since PHP4 is still extremely prevelant.

> My REAL question is whether this is a change in the LANGUAGE or 
> a "mere defect" in IMPLEMENATION. As defects go, it would be a doozy,
> and I don't like to see flip-flopping on something so important.

Beats me.  It is a "nasty" little bug.

> >http://tnx.nl/php
> I'd like to see the languages any of these guys wrote. Withut prejudice to
> any "side" in these discussions, it's a very instructive exercise, and provides
> a different perspective.

I'd like to see then review C#.  So far a language that answers just
about every gripe I've ever had.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://www.kalamazoolinux.org/pipermail/programming/attachments/20050408/ac5fc0a5/attachment.bin