Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:27086
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 213.239.212.54 cause and error)
Message-ID: <4587AC4C.7090308@php.net>
Date: Tue, 19 Dec 2006 10:09:32 +0100
User-Agent: Thunderbird 1.5.0.7 (X11/20060909)
MIME-Version: 1.0
To: Marian Kostadinov <manchokapitancho@gmail.com>
CC:  internals@lists.php.net
References: <bec76cf90612190022q6a89fc12m67b7516c2a26d687@mail.gmail.com>
In-Reply-To: <bec76cf90612190022q6a89fc12m67b7516c2a26d687@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] __toString extension proposal
From: colder@php.net (Etienne Kneuss)

Hi,

you can use:
class test2 {
    public function __toString(){ return (string) new test; }
}

Marian Kostadinov wrote:
> Hi,
> there is one issue that I experience since I started using 5.2.0 and
> especially the new correct __toString behaviour. Generally it works fine.
> But sometimes I find it useful to get __toString return another object 
> the
> also has a __toString method. So my idea is - is it possible (and good 
> idea)
> to make it work in this extended manner. Here is an example to illustrate
> what I mean:
>
> class test1 {
> function __toString() { return 'i am class 1'; }
> }
> class test2 {
> function __toString() { return new test1; }
> }
> $test = new test2;
> echo $test;
>


-- 
Etienne Kneuss
http://www.colder.ch
colder@php.net

Men never do evil so completely and cheerfully as 
when they do it from a religious conviction.
-- Pascal