Hi Pierre, On Thu, Mar 5, 2015 at 8:54 AM, Pierre Joye <pierre....@gmail.com> wrote:
> On Wed, Mar 4, 2015 at 1:36 PM, Yasuo Ohgaki <yohg...@ohgaki.net> wrote: > > Hi Leigh, > > > > On Thu, Mar 5, 2015 at 4:30 AM, Leigh <lei...@gmail.com> wrote: > > > >> On 1 March 2015 at 11:29, Yasuo Ohgaki <yohg...@ohgaki.net> wrote: > >> > > >> > Thoughts? > >> > > >> > >> require 'function_aliases.php'; // End of discussion. > >> > >> Maintain it however you want, set it up as a composer package, > >> whatever. Absolutely no reason for this to be in core, and absolutely > >> not worth the trouble it causes. > >> > >> Sorry if this has already been said, but I'm not going to read 60 > >> replies, most of which are probably spam. > >> > > > > Your reply is not a spam at all. > > I will do > > > > require 'function_aliases.php'; // End of discussion. > > > > If PHP has macro or userspace aliasing! > > This is one possible solution for this. > > > > We have class_alias(). We could have function_alias(). > > > > Regards, > > > > P.S. We still carry inconsistent names only, though. > > We may be better do this in PHP. IMHO. > > Is it not time to move to the vote? I am not seeing any value continue > this discussions. We clearly have two camps and I do not see a remote > chance to get them agreed on something (due to the nature of this > proposal). Let vote and move on. With the hope we will be done with > such topic for a while. There are many undecided issues in the RFC. I'll fix these, then start voting. Rowan suggested fixing other issues like parameter ordering. These may be addressed at once. If parameter ordering is fixed, new and old will be separate function. I need to research this issue. If there is good list of functions, I appreciate it. Regards, -- Yasuo Ohgaki yohg...@ohgaki.net
