Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59659
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F84587A.1090006@gmail.com>
References: <CAORXhGJwmbjw3Zze3+-oFA2Mb_Z-2owVESraNMMs57RzjRRMbA@mail.gmail.com>
	<-5877502932356715576@unknownmsgid>
	<CAORXhGLPdAie6UFq+daJhUmDUqp7RaFFLa596XdzdtuCddf0Jw@mail.gmail.com>
	<-3647345967307864634@unknownmsgid>
	<CAORXhGKjg_L11dFGNHNfNygDH018=ZhytAy1vH+Ei8QHfry=cA@mail.gmail.com>
	<CAORXhG+K3XML-47+FDYdL5D717wDX7c59Pz8KgqjcP16+Ad12w@mail.gmail.com>
	<4F831FAE.2030208@ralphschindler.com>
	<CALKFbxvLfQTT+VX7-9O8nqekMcQUjkR7PRofpwFvjMdgdJUaWA@mail.gmail.com>
	<4F8336CA.6030800@gmail.com>
	<-3946312978847986790@unknownmsgid>
	<4F84587A.1090006@gmail.com>
Date: Tue, 10 Apr 2012 10:22:29 -0700
Message-ID: <CALKFbxtV994mg0i3EviG1JCzK9PZWN8O=wk6yYAJr4y6FwVcbg@mail.gmail.com>
To: =?ISO-8859-1?Q?=C1ngel_Gonz=E1lez?= <keisial@gmail.com>
Cc: Luke Scott <luke@cywh.com>, PHP Developers Mailing List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: source files without opening tag
From: chrisstocktonaz@gmail.com (Chris Stockton)

Hello,

2012/4/10 =C1ngel Gonz=E1lez <keisial@gmail.com>:
> Luke Scott wrote:
>>> if ( version_compare(PHP_VERSION, '5.5', '<') )
>>> =A0include_once $file;
>>> else
>>> =A0require_code($file, array( 'once'=3D>true, 'warn' =3D> 'ignore' ) );
>> I'm fairly certain that wouldn't work either. Require and friends are
>> constructs, not functions.
>>
>> Luke
> I had assumed require_code would work with brackets around the parameters=
.
> Someone mentioned it, but you raise a good point in that it's not stated
> by the
> rfc, and would need to be explicitely supported.
>
> There are people calling require and friends with brackets, but that
> likely (ie.
> not looking at the lexer) works because the parameter is ('foo') which
> resolves
> as 'foo'. That wouldn't work when there are two of them.
> I think it should be something to consider when making the patch, though.
>
>

I understand your point that you are trying to make, but forward
compatibility I am not sure shares the same critical nature as
backwards. I think a software provider who is aiming at supporting a
wide variety of php versions is likely going to code around the lowest
common denominator. Even still, if they chose to they could have two
bootstrap files, one that included files with the new features and one
with the old.