http://www.geocrawler.com/mail/thread.php3?subject=%5BPHP-DEV%5D+__string_value%28%29++crashes+with+return&list=5
First of all I suggest everyone catches up on the reading :) Thies and I
were against it. Zeev wanted to keep it and most of the rest that replied
seemed to be against too.
Persona
At 20:08 22-08-01, Jeremy Bettis wrote:
>My implementation does not have these inconsistencies (I looked in the
>archives). The only wierd thing is print_r and dump_var.
I think the inconsistency that was there was that my implementation was for
displaying purposes only. If you call to_string(
My implementation does not have these inconsistencies (I looked in the
archives). The only wierd thing is print_r and dump_var.
"Zeev Suraski" <[EMAIL PROTECTED]> wrote in message
5.1.0.14.2.20010822195524.03aeb4c8@localhost">news:5.1.0.14.2.20010822195524.03aeb4c8@localhost...
> At 19:53 22-08-
At 19:53 22-08-01, Andrei Zmievski wrote:
>On Wed, 22 Aug 2001, Jeremy Bettis wrote:
> > I changed php (current CVS) to add another magic method to Objects,
> > __toString(). Whenever an object needs to be converted to a string,
> then it
> > will first try to call __toString() and if it can't,
On Wed, 22 Aug 2001, Jeremy Bettis wrote:
> I changed php (current CVS) to add another magic method to Objects,
> __toString(). Whenever an object needs to be converted to a string, then it
> will first try to call __toString() and if it can't, then it will just
> return "Object" like now.
Good
I changed php (current CVS) to add another magic method to Objects,
__toString(). Whenever an object needs to be converted to a string, then it
will first try to call __toString() and if it can't, then it will just
return "Object" like now.
Please look over my patch and see if I did it correctly
