Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59739
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.54 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F85A717.20405@lerdorf.com>
References: <CAGa2bXZ6G=Cphjrde3u1Mq3AAw-4yJk3s28vNe+Aybt2nGTumg@mail.gmail.com>
	<CAGa2bXZh4uMeUH_BSCFmfNgxS-SZC0svA9BPcSROjwmbfrtFyQ@mail.gmail.com>
	<CAGa2bXbhi4zdgd9Udo6KsoycDwg_Ke0Xe5h3_-fVDMvn_VfAjQ@mail.gmail.com>
	<A633CF2D7C7BED41B41F1E64F25507B806A5CDD6C2@MAILR001.mail.lan>
	<CAGa2bXZKfQ+HqOucwOnBH7gV84hpdxZb5qNY3t3ThF_zMKSGHw@mail.gmail.com>
	<4F850D06.10701@sugarcrm.com>
	<CAGa2bXZWrRh8RdMtKK_2_U_XmByC-O6hGRPrJyW5KwvE0CAK-w@mail.gmail.com>
	<4F8515AF.8060706@sugarcrm.com>
	<CAGa2bXZWudQeRm5h2eENGmgQDPfOqEmijB9-vPAvfKXLCfDiLw@mail.gmail.com>
	<4F851FE4.7000706@sugarcrm.com>
	<CAGa2bXbXdNcfHX_dM2EVVz_2JtS4cc+8pxneSLAd382TuQUg-w@mail.gmail.com>
	<4F8539E0.1090701@sugarcrm.com>
	<4F859063.1010401@lerdorf.com>
	<-3427386339833244777@unknownmsgid>
	<4F85A717.20405@lerdorf.com>
Date: Wed, 11 Apr 2012 10:37:45 -0700
Message-ID: <CAKOpQSwqTESZRzvqXepFv=6dfyOtwJzyBDJPi+HkxWjktVM=Sg@mail.gmail.com>
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: Luke Scott <luke@cywh.com>, Stas Malyshev <smalyshev@sugarcrm.com>, 
	Yasuo Ohgaki <yohgaki@ohgaki.net>, "internals@lists.php.net" <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=f46d0442811e763d2404bd6ab2fe
Subject: Re: [PHP-DEV] Re: Disabling PHP tags by php.ini and CLI options
From: kris.craig@gmail.com (Kris Craig)

--f46d0442811e763d2404bd6ab2fe
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Apr 11, 2012 at 8:45 AM, Rasmus Lerdorf <rasmus@lerdorf.com> wrote:

> On 04/11/2012 08:12 AM, Luke Scott wrote:
> > Tom has a "similar" RFC that has two modes:
> >
> > - Template mode - how it is now
> > - Code (or pure code) mode - <?php is only allowed at the top and is
> > optional. ?> is disallowed.
> >
> > Tom's RFC calls for template mode to remain the default, but allow you
> > to add a flag to require/include to interpret the script in "pure
> > mode". Allowing an optional starting <?php (only at top) maintains
> > backwards compatibility with most classes.
>
> And my objection to that is similar. An optional templating mode is the
> same as optional short_tags. it discourages template mode the same way
> short_tags are discouraged. For short_tags that discouragement makes
> sense. For templating it doesn't.
>

I have some objections to that RFC as well, but one question that comes to
my mind is, does allowing a "pure code" PHP mode really *discourage* use of
templating mode; and, if so, how?  From an MVC architectural standpoint, I
can actually see some benefit in having a type of code-only PHP file,
though Tom's current RFC negates that by allowing HTML bits to be included
upstream so I'll probably be voting it down anyway.  But conceptually, at
least, I think the idea has some merit IMHO.

--Kris


>
> -Rasmus
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--f46d0442811e763d2404bd6ab2fe--