Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55496
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mageekbox.net from 217.70.183.196 cause and error)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
In-Reply-To: <CAEZPtU4+ESV2XpXkUXvWyLs3b4Z7EFwD-E7=Ya9pN2PBuzUPVw@mail.gmail.com>
Date: Sun, 18 Sep 2011 14:26:58 +0200
Cc: RQuadling@gmail.com,
 Ferenc Kovacs <tyra3l@gmail.com>,
 Nikita Popov <nikita.ppv@googlemail.com>,
 PHP internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <8A2C4A73-0ECA-4EC0-A71D-BD28D1CCEA46@mageekbox.net>
References: <CAKUjMCXiYc63NKsUuYWXT-A-aPabdPV6142LP9h4-c=2aUxW=w@mail.gmail.com> <CAF+90c-YsWFtZVPajiUL6SKvde=EyVsSGAgWZrCCvT3Y9Q9YCw@mail.gmail.com> <CAH-PCH5YUjz-OkbJ=4ugUeaNjbAju+QXk65qtQ4cZ9dRxixV=A@mail.gmail.com> <CAKUjMCUjjVSf7XV6mr80nc_dTmELkd-2bb5=RoDueHs-ta2nLQ@mail.gmail.com> <CAEZPtU4+ESV2XpXkUXvWyLs3b4Z7EFwD-E7=Ya9pN2PBuzUPVw@mail.gmail.com>
To: Pierre Joye <pierre.php@gmail.com>
Subject: Re: [PHP-DEV] __constructor parameter limitations.
From: frederic.hardy@mageekbox.net (=?iso-8859-1?Q?Fr=E9d=E9ric_Hardy?=)

Hi !

> For one I do think that enforcing strictness, or as I see it, clean
> code and implementation, should be done in php. We did not do that in
> the past and it has created more issues than anything else in the long
> run.

+1.

> One solution to solve the need of having different methods or
> constructors signatures is to support multiple signature per method or
> constructor, as long as the signature of the parent class or interface
> is available. This is something becoming more and more common in other
> languages and is actually very handy. Having such things would have
> also avoided bad (per design while necessary) sutff like the recent
> reflection function to create objects without invoking the
> constructor.

+1.
The possibility to defined multiple signature per method will be a great =
improvement.

A class like this :

class foo
{
	function barForArray(array $array) {...}
	function barForACall(aCall $objectClass) {...}
	function barForCallable(Callable $callable) {...}
}

foreach ($arrayOfUndeterminedThings  as $data)
{
	switch (true)
	{
		case is_array($data):
			$foo->barForArray($data);
			break;

		case $data instanceof aCall:
			$foo->barForACall($data);
			break;

		case $data instanceof Callable:
			$foo->barForCallable($data);
			break;
	}
}

will become :

class foo
{
	function bar(array $array) {...}
	function bar(aCall $objectClass) {...}
	function bar(Callable $callable) {...}
}

foreach ($arrayOfUndeterminedThings  as $data)
{
	$foo->bar($data);
}

Best regards,
Fred
--
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Fr=E9d=E9ric Hardy : Architecte d'application/Admin. syst=E8me/Ergonome
                     CV : =
http://blog.mageekbox.net/public/cv.frederic.hardy.pdf
                  Blog : http://blog.mageekbox.net
              Twitter : http://twitter.com/mageekguy
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D