Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:32814
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mkj-computing.de from 213.239.209.74 cause and error)
Date: Tue, 16 Oct 2007 15:09:14 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C80FF5.C040856D"
Message-ID: <7C37FF3A0196094F95430BA95952032201611E@s1.mkj.lan>
Content-class: urn:content-classes:message
Thread-Topic: AW: AW: AW: [PHP-DEV] Method overloading by method signature
thread-index: AcgP8UjM4v2kh9sPRiWFURqI7sHRpgAAD0QU
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> <4714881F.1030302@cschneid.com> <7C37FF3A0196094F95430BA95952032201611B@s1.mkj.lan> <47149337.9000209@cschneid.com> <7C37FF3A0196094F95430BA95952032201611D@s1.mkj.lan> <C3712B89-CEAF-4328-B774-EA5DFB1147BB@pooteeweet.org>
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>,
	<internals@lists.php.net>
Subject: RE: AW: AW: AW: [PHP-DEV] Method overloading by method signature
From: hans.moog@mkj-computing.de ("Hans Moog")

------_=_NextPart_001_01C80FF5.C040856D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

>The point is that I do not see this feature at all relevant to =20
>solving the web problem. This is where PHP needs to focus. Namespaces =20
>help in solving the web problem, because it eases cooperation of =20
>independent developers to supply libraries. The feature you are =20
>proposing is solved easily in userland (just like named parameters). =20
>Its is a feature I could see using in a heavy lifting language, but =20
>not in a glue language. Where do we draw the line? Somewhere =20
>relatively arbitrary, but my gut tells me that this is a good =20
>candidate to be on "lets leave it out of php" side of the line.
>
>regards,
>Lukas

When it comes to interoperation between systems and or developers, it is =
always a
good idea to define strict standards of how the communication between =
libarys and components
has to take place (since public methods are something like an interface =
bewteen interoperating libraries and classes),
to be sure that all components work together as expected. One of the =
best approaches to
explain the usage of the class to a foreign developer and to be sure =
that your class is used
correctly and help the foreign developer to understand how your classes =
have to be used
(beside documentation), is to typehint your parameters.

But when you do so, you are no longer able to overload your methods =
anymore. Because of this, I think
this feature is EXTREMELY relevant to solving the web problem. Not being =
able to overload methods anymore
is a bad thing since overloaded methods allow to use a class in much =
more situations than just being able to use it
in one single way.

You are not able to tell the developer to use integer OR string values =
but NO arrays, booleans, Objects
and so on when calling your method.

You could mention it in the comment but when he misunderstands the =
comment, php doesn't notify him about
his error. When using type hinted parameters, php would do so.

You are not able to provide strict api's out of the box right now. You =
will always have to check the types of the
passed parameters manually.

------_=_NextPart_001_01C80FF5.C040856D--