Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46707
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain m.gmane.org designates 80.91.229.12 as permitted sender)
To: internals@lists.php.net
Followup-To:  gmane.comp.php.devel
Date:  Wed, 13 Jan 2010 11:06:56 -0600
Lines: 43
Message-ID: <hikuja$3qs$1@ger.gmane.org>
References:  <hij8pj$vbj$1@ger.gmane.org> <4B4D2883.5040703@lerdorf.com>
Mime-Version:  1.0
Content-Type:  text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding:  7Bit
Sender: news <news@ger.gmane.org>
Subject:  Re: [PHP-DEV]  Throwing an E_DEPRECATED for short_open_tag
From: geissert@debian.org (Raphael Geissert)

Rasmus Lerdorf wrote:

> Raphael Geissert wrote:
>> However, we would like to contribute in the quest to make applications
>> stop using short_open_tag. To do so, we have decided to throw an
>> E_DEPRECATED warning when an application makes use of short_open_tag. The
>> current implementation can be found at [1].
>> 
>> How does this sound?
> 
> We have no plans to deprecate the short open tag.  So throwing an
> E_DEPRECATED would not be appropriate.
> 

True. An idea I just had was to continue throwing E_DEPRECATED (or a warning 
with a most appropriate name, if one is added) iff short tags are used 
without explicitly enabling them at runtime.

I haven't looked at how the short_open_tag runtime switch was implemented so 
I don't know if it's possible or not.

This would for example make the following code throw a warning:

foo.php
<?
// ...
?>

But not this one:

bar.php
<?php
// ...
include("./foo.php");
?>

Does that sound more reasonable? or do you have another idea?

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net