Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:93843
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.17.20 as permitted sender)
To: Dominic Grostate <codekestrel@googlemail.com>,
 PHP internals <internals@lists.php.net>
References: <CAFKaYMq2cfNyhbfmAeaC8cetfnN9cvO_wy+EZVgNkZwAGju3JQ@mail.gmail.com>
Message-ID: <3589a101-3e9e-46e9-8d23-7f385646c0dc@gmx.de>
Date: Mon, 6 Jun 2016 15:17:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
In-Reply-To: <CAFKaYMq2cfNyhbfmAeaC8cetfnN9cvO_wy+EZVgNkZwAGju3JQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Opinion on function/method name overloading
From: cmbecker69@gmx.de (Christoph Becker)

Dominic Grostate wrote:

> As I understand it, using Java-like function overloading in PHP is
> undesirable due to hindrance in readability.
> 
> However I'd like to get an opinion on whether it would be received more
> favourably if it could provide an actual performance enhancement over hand
> managed implementation's of detecting argument differences with variadic
> and func_get_args.
> 
> On to a more subjective argument, "naming things" is hard, and I think many
> people would appreciate being able to reuse function/method names without
> sacrificing type safety.

Another issue besides what has already been mentioned in other replies
is that PHP already has the concept of overloading[1]:

| Overloading in PHP provides means to dynamically "create" properties
| and methods. These dynamic entities are processed via magic methods
| one can establish in a class for various action types.

So at least another name would have to be chosen for either of both
concepts.

[1] <http://php.net/manual/en/language.oop5.overloading.php>

-- 
Christoph M. Becker