Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:46753 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85335 invoked from network); 16 Jan 2010 17:16:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 16 Jan 2010 17:16:57 -0000 Authentication-Results: pb1.pair.com header.from=rasmus@lerdorf.com; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=rasmus@lerdorf.com; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain lerdorf.com from 209.85.211.202 cause and error) X-PHP-List-Original-Sender: rasmus@lerdorf.com X-Host-Fingerprint: 209.85.211.202 mail-yw0-f202.google.com Received: from [209.85.211.202] ([209.85.211.202:44717] helo=mail-yw0-f202.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id C3/59-27028-884F15B4 for ; Sat, 16 Jan 2010 12:16:57 -0500 Received: by ywh40 with SMTP id 40so1459749ywh.26 for ; Sat, 16 Jan 2010 09:16:54 -0800 (PST) Received: by 10.101.139.24 with SMTP id r24mr6444167ann.182.1263662214128; Sat, 16 Jan 2010 09:16:54 -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 9sm96489yxf.41.2010.01.16.09.16.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 16 Jan 2010 09:16:52 -0800 (PST) Message-ID: <4B51F482.7050802@lerdorf.com> Date: Sat, 16 Jan 2010 09:16:50 -0800 User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Raphael Geissert CC: internals@lists.php.net References: 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: > Patrick ALLAERT wrote: > >> 2010/1/13 Derick Rethans : >>> On Tue, 12 Jan 2010, Raphael Geissert wrote: >> [snip] >> >>> Would it be possible to force short_open_tag to a specific value for >>> those applications alone? Perhaps through an .htaccess file? That way, >>> Debian keeps the "PHP default" but still allows those apps to work. >> Raphael, you didn't seem to react on Derick's suggestion above >> although it seems one of the best proposition so far. >> > > I sort of commented about it on one of my replies to Rasmus. The problem > with that approach is that not all SAPIs can be configured via a .htaccess, > and changing the global value affects all applications (and if they all use > a SAPI where .htaccess files can't change the settings there's not much they > can do). I think you are again becoming a victim of too much generalization. Like using the slower re-entrant mysql client library, for example, just in case you have a threaded SAPI that needs it. 99% of people are going to be using the prefork Apache SAPI or fastcgi, neither of which needs this, and thus you are penalizing the majority in order to support edge cases more easily. Same goes for per-package configuration. The common case, Apache and fastcgi, can do per-directory configuration, but you are choosing not to use it in order to support edge cases. Instead of trying to change PHP here, I'd be going after your problematic edge cases and bringing them up to speed so they can support per-app configuration. -Rasmus