Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51071
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.182 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=N9/xOTTlqQdzxMB4CJO92BdY5ayUZ1fa/MF05lCRAPjewSAPIur6r/wKonTmAgFiWl
         m8Vs7TpqLO6GiaVq17kCuLmSht4dsxmVsV/K49wRR3Y2RerAigAxehtaJXDb/TTUNHak
         3+eN48I5rqhJUpozUxAs/rZztjDMkcyK+Gy70=
MIME-Version: 1.0
In-Reply-To: <AANLkTikWg_oQRF8yR9xMjjFMcojmGuzdXAjborhpqrk8@mail.gmail.com>
References: <AANLkTim-Ekq=UeY-TXtryrbjR9=JpJOuPceTUaP5y0Rp@mail.gmail.com>
	<AANLkTikWg_oQRF8yR9xMjjFMcojmGuzdXAjborhpqrk8@mail.gmail.com>
Date: Fri, 17 Dec 2010 20:27:45 -0800
Message-ID: <AANLkTi=PRMrj9CO9J8V-vxQ1Aq2ykv-g0M3M_1ssZNKJ@mail.gmail.com>
To: Michael Morris <dmgx.michael@gmail.com>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] RFC: Selecting Namespaces and Tag styles at include
 time. ( was Re: PHP Dev RFC Selecting Namespaces and Tag styles at include time.)
From: ssufficool@gmail.com (Stanley Sufficool)

I would go with a maskable enumeration for multiple options support:

Val  Constant
0    PHP_TAGS_NONE
1    PHP_TAGS_LEGACY
2    PHP_TAGS_STANDARD
4    PHP_TAGS_SHORT
8    PHP_TAGS_SCRIPT
16    PHP_TAGS_ASP

So that if I want to use mixed tags (<?php and <?) then I can set

tag_style =3D PHP_TAGS_SHORT | PHP_TAGS_STANDARD
or
tag style =3D 6

IMHO, I think is more flexible and understandable.

On Fri, Dec 17, 2010 at 10:09 AM, Michael Morris <dmgx.michael@gmail.com> w=
rote:
> I've been giving some thought to the implication of my off the cuff addit=
ion
> of PHP_TAGS_NONE to the modes allowed and what should logically go with
> that. If tag style can be declared in a function, it should be possible s=
et
> them in the configuration and at other places. Currently tag style is spr=
ead
> over multiple settings in the configuration - I know of two:
>
> asp_tags
> short_open_tag
>
> This is problematic moving forward so I hereby suggest nipping further
> proliferation in the bud and go to one configuration setting with this na=
me:
>
> tag_style
>
> It's values, and their corresponding meaning:
>
> Val =A0Constant =A0 =A0 =A0 =A0 =A0 Effect
> 0 =A0 =A0PHP_TAGS_LEGACY =A0 =A0Honor older ini tag settings such as asp_=
tags
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 or short_open_tag, in all=
 ways behave in a
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 a manner compliant with t=
he expectations of
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 any scripts that are upgr=
ading.
> 1 =A0 =A0PHP_TAGS_NONE =A0 =A0 =A0No tags will be permitted in the file.
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Interpreter expects the w=
hole file to be
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PHP.
> 2 =A0 =A0PHP_TAGS_STANDARD =A0Enable the classic <?php ?> tags we all kno=
w
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 and love.
> 3 =A0 =A0PHP_TAGS_SHORT =A0 =A0 Use PHP short tags <? ?> and <?=3D ?>. Un=
like
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Legacy behavior with shor=
t_open_tag set to
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 'on' this setting will NO=
T let you use
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <?php ?> alongside the <?=
 ?> and <?=3D ?>
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 tags.
> 4 =A0 =A0PHP_TAGS_SCRIPT =A0 =A0Script tags <script type=3D"php"></script=
>
> 5 =A0 =A0PHP_TAGS_ASP =A0 =A0 =A0 ASP style tags <% %>
>
> And so a script could have an .htaccess file with
>
> php_flag php_tags 1
>
> So the first file the webserver reads in doesn't have to have any opening
> tag at all. This would put a stop to the puzzlement of "Why am I getting =
an
> error when I call header()" which I see on programming boards at least on=
ce
> a week.
>
> The constants above can in turn be coupled to my original recommendation
> that include, include_once, require, and require_once each be allowed to
> have a second parameter. The default value of the second parmeter is
> whatever php_tags is set to at the time the include statement is parsed.
>
> Hence, unlike the current situation with short_open_tag and asp_tag,
> php_tags can be changed at runtime using ini_set. The only catch is the
> change only affects includes which occur after the setting change.
>
> I believe strongly that this improved recommendation improves the
> interoperability of tag styles without creating backwards compatibility
> issues or creating future problems. =A0As for the secondary suggestion I =
made,
> allowing namespaces to be specified in the include statement, I'll drop t=
hat
> from this recommendation to focus on the changes to tag style setting.
>