Date: 08/31/00
- Next message: Jon Parise: "Re: [PHP-DEV] __string_value() crashes with return"
- Previous message: Sterling Hughes: "Re: [PHP-DEV] getimagesize() with full url??"
- In reply to: Derick Rethans: "Re: [PHP-DEV] __string_value() crashes with return"
- Next in thread: Jon Parise: "Re: [PHP-DEV] __string_value() crashes with return"
- Reply: Jon Parise: "Re: [PHP-DEV] __string_value() crashes with return"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> Andi Gutmans wrote:
>
> > Well I can see no one can decide what to do with __string_value().
> > Thies and I would like to see it removed and Zeev and some other folks
> > would like to keep it in.
> > I think it is a bit dumb to keep it in just so that print $obj will be
> > easier to type than print $obj->toString() especially as
> __string_value()
> > works and only will work in future with print.
> > How do we resolve this and decide? :)
>
> Remove it. Programmers are being too lazy already, and this
> "functionaly" is
> somewhat "fuzzy". I think there will be a lot of questions like: why does
> "(string) $object" not work, and so.
I agree. Get rid of it now, while the gettin' is good.
.mike
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Jon Parise: "Re: [PHP-DEV] __string_value() crashes with return"
- Previous message: Sterling Hughes: "Re: [PHP-DEV] getimagesize() with full url??"
- In reply to: Derick Rethans: "Re: [PHP-DEV] __string_value() crashes with return"
- Next in thread: Jon Parise: "Re: [PHP-DEV] __string_value() crashes with return"
- Reply: Jon Parise: "Re: [PHP-DEV] __string_value() crashes with return"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

