Re: __string_value() crashes with return

At 17:27 30-08-00, Stanislav Malyshev wrote:

I´d say you should follow the rules and write some 'string' into it, even variables are not allowed I suppose

    i'm for removing the __string_value() call alltogether!

<aol>me too!</aol> But won't this break someone's scripts? As far as I see, this thing is there for pretty long time, not (for a year at least)?

It's been around for about half a year. I don't see any real downsides to it, other than having to explain that it's *NOT* an underpowered operator overloading which suggests we'll go towards this area in the future, but rather, a handy facility to debug object code.

But at the very least, the __string_value should be fixed not to crash on non-string values!

It probably just doesn't convert it to a string. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/