Hello Ron, i had a chat with Andi about __toString() and i hope that he finally undestood why a lot of ppl wanted it right from the beginning. To me the current situation is simply the worst case because noone understnds when it works and when not (. vs ,). Since we are doing a drastic change in string behavior anyway and this time have enough time until next release i already agreed on taking care about this one as early as possible. This way we will have enough time to find any places where __toString() is not possible. Also Andi and i discussed again the major problem and i could ensure Andi that there is a simple solution which he agreed on. That is we require __toString() to return a string and do a non interruptable halt otherwise. Maybe in a later version this can be replaced by an exception we'll see if someone finds the time to analyse that in detail.
best regards marcus Wednesday, August 10, 2005, 4:50:17 PM, you wrote: > Exactly. That's how I understood it too: "Ah, the __toString behavior". I'm > very glad this is not the case. > Ron > "George Schlossnagle" <[EMAIL PROTECTED]> schreef in bericht > news:[EMAIL PROTECTED] >> >> On Aug 10, 2005, at 10:30 AM, Rasmus Lerdorf wrote: >> >> > Yeah, print/echo was just a way of describing the underlying output >> > stuff. It wasn't meant to be taken literally. >> >> Given the __toString fiasco, it's understandable that this would be >> confusing though. >> >> George Best regards, Marcus -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
