Hi,

2012/4/12 Rasmus Lerdorf <ras...@lerdorf.com>:
> On 04/11/2012 02:10 PM, Yasuo Ohgaki wrote:
>> It's also very easy to write backward compatible code also.
>> The 3 lines of changes to adopt this RFC do not bother
>> old PHP.
>>
>> No compatibility issue for existing code
>> Just 3 lines of change to adopt
>> Full backward compatibility for OLD systems
>>
>> The only issue is NEW code may be disclosed by **OLD**
>> systems.
>>
>> 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?
>

I guess you have been writing code for the best performance.
I have these code also. For these codes, there are many places
to change, so it can't be adopt template_mode=off easily.

The best way would be defining your own include/require wrapped
by ini_set('template_mode', 'on') and ini_set('template_mode', 'off');
Then replace include/require where it is needed.

Users may stay template_mode=on. The best part of PHP is
templating, so this switch should be in PHP forever. This switch
is to enjoy best of both embedded and non-embedded language
at the same time. PHP without template is not PHP.

I would rather not to have new parameters nor special extensions
for PHP only script. This RFC is the best I can think of now.

Regards,

--
Yasuo Ohgaki
yohg...@ohgaki.net

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to