Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:51106
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.216.42 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:reply-to:in-reply-to:references:from:date:message-id
         :subject:to:cc:content-type:content-transfer-encoding;
        b=sBT5O+69XEw2ss+MO0IWrO0ePxfIi7Z2z1IA/o/LWJ3wSvkp3Fig2/WMABIjN7YkFJ
         GbtHwfV/Ji+HL46Ashz6Ezf81l42KDMgaQDZqHdEFtF6tIWQ2o6wNAQGoa5Hd+oAnvE+
         6NUHUM8Ygh+4XBYcxXhKEhChvbZxTbsJ7qSPo=
MIME-Version: 1.0
Reply-To: RQuadling@googlemail.com
In-Reply-To: <AANLkTimoajnug41On91jB6p=nkyF_rmAtYmS3mUUy1N9@mail.gmail.com>
References: <AANLkTim-Ekq=UeY-TXtryrbjR9=JpJOuPceTUaP5y0Rp@mail.gmail.com>
 <AANLkTikWg_oQRF8yR9xMjjFMcojmGuzdXAjborhpqrk8@mail.gmail.com>
 <F3.1D.35939.1513E0D4@pb1.pair.com> <AANLkTik6UFNcBZU2n5coq24m-DznZkG1p16CfRwPYRf4@mail.gmail.com>
 <AANLkTin9oWif8cVvJV+AcwPpKYGucYOwz2XTOiGDfkiQ@mail.gmail.com> <AANLkTimoajnug41On91jB6p=nkyF_rmAtYmS3mUUy1N9@mail.gmail.com>
Date: Tue, 21 Dec 2010 16:15:12 +0000
Message-ID: <AANLkTi=4Mkot7HAt163QSYhckzAsEf6v6ybEU0APN0Pg@mail.gmail.com>
To: Michael Morris <dmgx.michael@gmail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
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: rquadling@gmail.com (Richard Quadling)

On 21 December 2010 16:00, Michael Morris <dmgx.michael@gmail.com> wrote:
> Uhm, If bit 0 is set to 0, and all the higher bits are also set to 0, the=
n
> the total value of the field is 0.
>
> Under this scheme bit 0 is the legacy mode bit. =C2=A0Turn it off and PHP=
 will
> parse tags according to historical behavior and respects the asp_tags and
> short_open_tags flag. =C2=A0Turn it on and those behaviors go away. =C2=
=A0The weird
> part about this particular bit is you have to turn it on in order to turn
> something off. I don't like doing that, but I don't see another way to ke=
ep
> backwards compatibility since PHP should act as it currently does if this
> setting isn't set or is left at '0'.

Would it not be feasible to drop asp_tags and short_open_tags,
replacing them with the new entry and have the default value of the
entry set so that it is corresponds to the default values of the
asp_tags and short_open_tags?

As the default (based upon php.ini-development and php.ini-production)
is to set asp_tags and short_open_tags to off, it would seem that a
new ini entry, replacing the older tags, doesn't need to worry about
the value in the recommended/default position.

Alternatively, could the default value (for when there isn't one
defined in a current ini file) simply be based upon whatever is set
for asp_tags and short_open_tags? Essentially, subsuming the older
settings into the new one and allowing a sysadmin/developer to set the
value if they want to.

I don't think it would be necessary to support the old style settings
if the change was done at a major version, though asp_tags and
short_open_tags could be marked as deprecated in the next minor
release.



--=20
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY