Re: Re: Disabling PHP tags by php.ini and CLI options
| From: | Yasuo Ohgaki | Date: | Fri, 13 Apr 2012 00:48:15 +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-59824@lists.php.net to get a copy of this message | ||
Hi,
2012/4/13 David Muir <davidkmuir@gmail.com>:
> On 13/04/12 10:02, Arvids Godjuks wrote:
>> 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!
>>
>
> I was wondering when someone was going to point that out. ;-)
>
> David
I've said "PHP without templating is not PHP", too. :)
I would like to save current code as much as it can, so I prefer
php.ini switch over other method.
If I exclude current code, then introducing script only include will be
preferred one. I preferred dedicated statement for it though.
include
include_once
require
require_once
script
script_once
something like this. And for CLI switch, of course.
Framework developers can use define script/script_once
function script($file) {
require($file);
}
function script_once($file) {
require_once($file);
}
like this for compatibility.
Regards,
--
Yasuo Ohgaki