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

From: Date: Thu, 12 Apr 2012 22:48:47 +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 18  Groups: php.internals 
Request: Send a blank email to internals+get-59806@lists.php.net to get a copy of this message
Hi, 2012/4/12 Lester Caine <lester@lsces.co.uk>: > Rasmus Lerdorf wrote: >>> >>> If you think it costs too much still, please let me know. >> >> Pretty much all of the code I have ever written would break. I use >> PHP-based templating everywhere and include my templates with >> include/require. How exactly can I fix this with 3 lines of code? > > > Nice to hear that I'm not alone in using 'simple' templating. > I've also scanned a few of the sites I support, and it's quite surprising > just how many STILL use short open tag! > Once again - if people really want a 'programming language' will they please > start a separate fork! Leave those of us who are happy with what we have > with something that just works out of the box ( and even 'STRICT' is pigging > annoying ) Then this RFC would be better RFC than the other. This RFC encourage to write "<?php" at the top always while other has special parameter and file extension for script only files which will certainly lead full of "<?php" less scripts. We can use PHP for simple/efficient templating as it is now and still can include third party library files since "<?php" will be there. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net

« previous php.internals (#59806) next »