Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60011
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 209.85.217.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F8C757C.1020400@developersdesk.com>
References: <CAEZPtU52Ayb6fnLSaZdQ+LHk1hEh3X1tJUO3NWUg3befgSAM1w@mail.gmail.com>
	<CAGa2bXZ6W7=Pi+SP4b6c510bWbM9hEjq90_s63bBxbc9n9vsoQ@mail.gmail.com>
	<CAKOpQSxAd6sG8BHWn+dUUz4rAdChhUA+HXyJGpeoZ8GmJKRM0w@mail.gmail.com>
	<CAL0xaBGSbBAw3XEwzNOxzoNoFAHDQVDFH9Zw7ju5VKNtA12UYA@mail.gmail.com>
	<CAH-PCH7qjnwQk1kvOYg67tU-p+YSV8za6-k-56JYXiu1xSHHxQ@mail.gmail.com>
	<CAL0xaBHo0aTCBEM9YRbXs8nQAC5t5CnHEo=nBaGyNVVMfZ03MQ@mail.gmail.com>
	<4F8C577D.4010303@developersdesk.com>
	<CAKOpQSz8eiJmnwWhunsEY_ZFuUYXQjcibZ-gvBe52v1-q3-GUw@mail.gmail.com>
	<4F8C757C.1020400@developersdesk.com>
Date: Mon, 16 Apr 2012 21:51:34 +0200
Message-ID: <CAF+90c8nLnViURirnmrPY78rfrkbQQmf+JnZAevJYDjnp5G0aA@mail.gmail.com>
To: Rick WIdmer <vchkpw@developersdesk.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Re: Go for votes for the open tag-less PHP files
From: nikita.ppv@googlemail.com (Nikita Popov)

On Mon, Apr 16, 2012 at 9:39 PM, Rick WIdmer <vchkpw@developersdesk.com> wr=
ote:
> On 4/16/2012 1:02 PM, Kris Craig wrote:
>>
>> On Mon, Apr 16, 2012 at 10:31 AM, Rick
>> WIdmer<vchkpw@developersdesk.com>wrote:
>>>
>>>
>>> More important include doesn't currently allow multiple parms:
>>>
>>> =A0 include "foo.bar", 'baz';
>>>
>>> Parse error: syntax error, unexpected ',' in bla.php on line xx
>> Regarding include/require, I agree that any BC break would be extremely
>> minimal. =A0In the 10+ years I've been developing PHP, I don't think I'v=
e
>> ever once seen somebody include multiple scripts on a single line (I
>> wasn't even aware that such a thing was allowed).
> See above. =A0It is not allowed now.

I think there is a misunderstanding here. Inclusions with two
arguments are currently not allowed, yes. The point is that adding
such a second argument would make the grammar ambiguous.

E.g, consider this:

func(include 'foo', $someThing);

Currently this is interpreted as the return value of 'foo' and the
variable $someThing being passed to func.

If you add a second argument it's unclear what this does. Is this a
two-argument include? I.e. should it be interpreted as

func((include 'foo', $someThing));

Or is this a one-argument include and should be interpreted as

func((include 'foo'), $someThing);

In my eyes such an ambiguity renders any proposal to add another
argument to include completely unacceptable.

The only option is to add a dedicated syntax for it like

include 'foo' as $flags;

Nikita