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

On Thu, Apr 12, 2012 at 5:02 PM, Arvids Godjuks <arvids.godjuks@gmail.com>wrote: > You all know where the short_tags, register_globals, magic_quotes and other > stuff like that took the language and the problems it made. > Doesn`t history teach us a lesson? I see that it did not for some active > members of this list. > Many are still cleaning up the mess of thouse optional php.ini directives, > Ibhad to clean up myself one project, took me 2 months to properly fix it > and make to run on PHP 5, anyway we ended up rewriting the whole thing from > scratch, a year of day to day work. > Now i write my stuff E_ALL, including strict stuff and I know for a fact > that there is no php.ini switch that could screw up my applications on > different hosting platforms (yes, some minor things can happen in specific > situations, but any properly configured PHP 5.3/5.4 will run smooth). And > now you purpose to add a switch that in one line can disable the > application for good (and get it's sources spit out all over the place). > And even if i write it in the right way - i have to convert every damn > external library. Ok, i upload it to the host and guess what - it spews the > code out because it is configured for the <?php tag! > > It will never get adopted, too many legacy stuff, to many external tools. > And php native templates? I dont neet any twig, smarty or any other stuff. > And guess what - most template engines cache compiled templates, and they > are - ta-daa - PHP EMBEDDED IN HTML CODE! > > Common sence is allien to some people on this list or what? > As is civility and basic mutual respect, it would seem.