Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59526
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: <4F831FAE.2030208@ralphschindler.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>
Date: Mon, 9 Apr 2012 11:23:16 -0700
Message-ID: <CALKFbxvLfQTT+VX7-9O8nqekMcQUjkR7PRofpwFvjMdgdJUaWA@mail.gmail.com>
To: Ralph Schindler <ralph@ralphschindler.com>
Cc: 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,

On Mon, Apr 9, 2012 at 10:43 AM, Ralph Schindler
<ralph@ralphschindler.com> wrote:
> Hey Tom,
>
> An idea, why not overload require/include with a second parameter that
> simply enforces an include mode. =A0For example
>
> // in some autoloader (include, requires, and *_onces)
> include $pathToFile, INCLUDE_MODE_PHP_ONLY;
>
> This would tell the parser/executor to start in PHP mode and never leave =
it,
> that way, ending tags would throw a runtime/execution error.
>
> Other constants and behaviors could be:
>
> =A0INCLUDE_MODE_PHP_START;
> =A0INCLUDE_MODE_PASSTRHOUGH_START; (the current and default behavior)
>
> This would have the least amount of impact on BC, and seeminlyg would be =
a
> friendly change to the lexer/syntax.
>
> Thoughts?
>
> -ralph
>
>

Although I am not very interested in this feature, if it is
implemented I like the idea of flags instead of introducing new
keywords. Maintaining backwards compatibility would be great
considering the benefit to the feature to be completely honest (and in
disagreement to many people, but I do understand the reasoning for
everyone's interest in it) is extremely minor in my eyes.

In addition I would suggest maybe using PHP_INCLUDE_* as a place for
these constants to live.

-Chris