Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:80991
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.170 as permitted sender)
Message-ID: <54C161BF.4090004@gmail.com>
Date: Thu, 22 Jan 2015 12:46:55 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0
MIME-Version: 1.0
To: Andrea Faulds <ajf@ajf.me>, Adam Harvey <aharvey@php.net>
CC: Marc Bennewitz <dev@mabe.berlin>, 
 PHP internals <internals@lists.php.net>,
 julien pauli <jpauli@php.net>
References: <54BEC072.5000507@mabe.berlin> <CADajX4AX0ZgHRmUvXWjkUkXLbBcvKmopY+T+dozE-M08asQojQ@mail.gmail.com> <C65F205B-10AE-4692-9670-DB6D32E9C88C@ajf.me>
In-Reply-To: <C65F205B-10AE-4692-9670-DB6D32E9C88C@ajf.me>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Inconsistencies in callable, call_user_func and direct
 variable calls
From: smalyshev@gmail.com (Stanislav Malyshev)

Hi!

> It’s technically a 'language change’ and would affect the language
> specification. That said, it seems rather “no-brainer”.

I think it makes a lot of sense to have call_user_func() and $a() work
identically. I'm not sure though if it should be done by adding
'foo::bar' to $a() or removing it from call_user_func(). Adding means
stuff that wasn't callable before may be callable now which may expose
the code for some issues (though if you allow people to call arbitrary
functions in your code you're probably in trouble anyway, so it may not
be a big deal).

I think it's better to have an RFC which clearly states what is
added/removed and that call_user_func()/$a()/is_callable/callable
type/whatever else uses it - are all in sync after it and preferably use
the same code, and have tests for all options supported.
-- 
Stas Malyshev
smalyshev@gmail.com