> WF>> The reason I mentioned this is that serialize($obj) is currently > WF>> meaningless for COM objects, so people are using > WF>> serialize((string)$obj) to get a string representation. > > I don't understand - what is the meaning of serialize((string)$obj)? What > should it return?
Just pretend I didn't mention serialization... you're getting off topic :-) What I'm trying to say is that (string)$obj really should work (as it does currently) for overloaded objects because they might not have a __toString() method, and if they do, we shouldn't overload it in PHP with some kludge method because we will probably get it wrong (just take a look at the kind of kludge we have for IEnumVariant support in the 4.x COM extension!). --Wez -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
