Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32826
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.132.246 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=YWEe6k54NXrfCJ0ZvYLVKn8TX1CrSkPm02dLTbGHB+AvldafaiynB4X+ecoZ+ew6GR+MJ0/IiTg/h+eJvrxLgqaSBaxRhPyI5REtLy17dc7Os5HUajPK/9SUf4HZwm1fueoJAFjcm5cAC0zZsp15BgX19b2XCzooY49y7wLJ0QI=
Message-ID: <10845a340710170523k55f7b956l61119b491e9a6c73@mail.gmail.com>
Date: Wed, 17 Oct 2007 13:23:26 +0100
Reply-To: RQuadling@GoogleMail.com
To: "Stanislav Malyshev" <stas@zend.com>
Cc: internals@lists.php.net
In-Reply-To: <471553FE.8060700@zend.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <7C37FF3A0196094F95430BA95952032211B7C5@s1.mkj.lan>
	 <cd5680a20710131322k110ee1e4q9194d8390df398f3@mail.gmail.com>
	 <7C37FF3A0196094F95430BA95952032211B7C7@s1.mkj.lan>
	 <72129346.20071014092922@marcus-boerger.de>
	 <7C37FF3A0196094F95430BA95952032211B7CC@s1.mkj.lan>
	 <19939840.20071014231353@marcus-boerger.de>
	 <002f01c80f5b$d645d340$15b2a8c0@unterwegs>
	 <7C37FF3A0196094F95430BA95952032211B7D2@s1.mkj.lan>
	 <10845a340710160150k31faebdv69d6c33939024a4f@mail.gmail.com>
	 <471553FE.8060700@zend.com>
Subject: Re: [PHP-DEV] Method overloading by method signature
From: rquadling@googlemail.com ("Richard Quadling")

On 17/10/2007, Stanislav Malyshev <stas@zend.com> wrote:
> > suit fully fitted) "catch-up". (Hey when has documentation EVER been
> > ahead of the game!?!).
>
> Always? Otherwise there would be no need for documentation, if
> everything was in the code. Some people even start with writing docs and
> only then implement the actual code. Of course, it is not always the
> case (and some code, like Zend Engine, is so obvious that no docs are
> needed anyway ;) but documentation containing more insight and more
> content than the pure code is almost always the case, especially with
> properly documented code.

So all I need to do is document this great new feature, hope no-one
notices and then come screaming saying that it doesn't work as
documented.

Hmm.

Possibly not a good way to make friends and influence people.

This feature, along with property accessibility via some sort of
read/write mechanism would be more useful to me than some other
features (like cough-cough unicode cough-cough).

It is something I am familiar with in other languages.
-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"