Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46708 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 11565 invoked from network); 13 Jan 2010 17:13:52 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jan 2010 17:13:52 -0000 Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.220.227 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.220.227 mail-fx0-f227.google.com Received: from [209.85.220.227] ([209.85.220.227:36441] helo=mail-fx0-f227.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E0/1C-00773-F4FFD4B4 for ; Wed, 13 Jan 2010 12:13:52 -0500 Received: by fxm27 with SMTP id 27so762050fxm.23 for ; Wed, 13 Jan 2010 09:13:48 -0800 (PST) Received: by 10.223.17.19 with SMTP id q19mr2738398faa.75.1263402828397; Wed, 13 Jan 2010 09:13:48 -0800 (PST) Received: from ?192.168.200.22? (c-98-234-184-167.hsd1.ca.comcast.net [98.234.184.167]) by mx.google.com with ESMTPS id 15sm1000788fxm.10.2010.01.13.09.13.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 13 Jan 2010 09:13:47 -0800 (PST) Message-ID: <4B4DFF46.7060908@lerdorf.com> Date: Wed, 13 Jan 2010 09:13:42 -0800 User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Raphael Geissert CC: internals@lists.php.net References: <4B4D2883.5040703@lerdorf.com> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Throwing an E_DEPRECATED for short_open_tag From: rasmus@lerdorf.com (Rasmus Lerdorf) Raphael Geissert wrote: > 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 > // ... > include("./foo.php"); > ?> > > Does that sound more reasonable? or do you have another idea? Then we have to have logic to differentiate