Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23899
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7.0.1.0.2.20060603181129.0396fc18@zend.com>
Date: Sat, 03 Jun 2006 18:12:33 -0700
To: pierre.php@gmail.com
Cc: internals@lists.php.net
In-Reply-To: <20060604030100.1093d2f9@pierre-u64>
References: <795156743.20060603134212@marcus-boerger.de>
	<20060603143639.GF5355@desario.homelinux.net>
	<509342741.20060603183859@marcus-boerger.de>
	<7.0.1.0.2.20060603175211.02208a50@zend.com>
	<20060604030100.1093d2f9@pierre-u64>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] Missing __toString() part
From: andi@zend.com (Andi Gutmans)

Yep that is also a choice, although it can be advantageous to have an 
automatic (a) which people just now works, always...
I don't think it's a critical problem because as you pointed out 
people can deal with it, but I think it'd be nice to provide some 
tools to make life easier.


At 06:01 PM 6/3/2006, Pierre wrote:
>Hi,
>
>On 6/4/06, Andi Gutmans <andi@zend.com> wrote:
> > Generally I think it's a good thing to allow to use objects as array
> > indexes. There are really two ways of doing it:
> > a) Try and find a way to create unique ideas.
> > b) Support __toString() and leave it up to the author.
>
>I see a third choice, which I prefer:
>
>c) leave the choice to the user, he knows better what to do with his
>    object (like implementing his own get(Hash|Key) method.
>
>
>--Pierre