Re: Re: Disabling PHP tags by php.ini and CLI options

From: Date: Fri, 13 Apr 2012 05:22:39 +0000
Subject: Re: Re: Disabling PHP tags by php.ini and CLI options
References: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17  Groups: php.internals 
Request: Send a blank email to internals+get-59853@lists.php.net to get a copy of this message
On 13/04/12 14:55, Stas Malyshev wrote: > Hi! > >> If this is a pecl module library developers cannot use it and trust >> that on php 5.n, it just works. That would fork the language in an >> undesirable way. It should be a core feature, no ini flag, no >> sometimes-there module. > PHP 5.n is at least a year away, wide adoption of it - more like 5 years > away. So if you want to write code that would run anywhere (as opposed > on systems you control) you'd have to wait minimum 5 years. Wouldn't it > better to have it earlier? > OTOH, requiring extensions is a common thing for applications, and any > pecl extension is one command away for most setups, or one download away > for others. And can be made work even in 5.2 if desired. Can't it also be handled using streams to inject a leading <?php to the file prior to inclusion? A PECL extension would then just make it run a bit faster. Cheers, David

« previous php.internals (#59853) next »