[TYPO3-core] RFC: Bugfix #7425: syntax error in temp_CACHE*.php

[Steffen Kamper]

"Martin Kutschker" <Martin.Kutschker at n0spam-blackbox.net> schrieb im 
Newsbeitrag 
news:mailman.1.1202378493.8086.typo3-team-core at lists.netfielders.de...
> Steffen Kamper schrieb:
>> "Martin Kutschker" <Martin.Kutschker at n0spam-blackbox.net> schrieb im 
>> Newsbeitrag 
>> news:mailman.1.1202373200.6813.typo3-team-core at lists.netfielders.de...
>>> Steffen Kamper schrieb:
>>>> This is a SVN patch request.
>>>>
>>>> Branches: Trunk only
>>>>
>>>> BT reference: http://bugs.typo3.org/view.php?id=7425
>>>>
>>>> Type: Bugfix
>>>>
>>>> Problem:
>>>>
>>>> if extensions ext_localconf.php or ext_tables.php misses php endtag, 
>>>> there is a syntax error in temp_CACHE*.php because they are merged 
>>>> together, and then such a construct leads to the syntax error:
>>>>
>>>> <?php
>>>> ...
>>>> <?php
>>>>
>>>> Solution:
>>>>
>>>> strip out php-tags and wrap with single php-tag
>>> Any PHP error in ext_localconf.php or ext_tables.php will break the 
>>> caches. This happens only during development. Any extension that comes 
>>> with broken configuration files is seriously flawed. We should not get 
>>> developer get away with that.
>>>
>>> So -1.
>>>
>>> But what would be nice, if TYPO3 would stop gracefully and tell the 
>>> admin which extensions ist to be removed manually from localconf.php
>>>
>>> Masi
>>
>> i think we clarified that leaving out end tag of php is not an error, 
>> it's recommended in docs for some reasons.
>
> Did we? From reading I'd give you a +1 one the code, but I really would 
> like to see some kind of official statement that we don't require a 
> closing php tag. Looks like a sloppy coding style in my opionion, 
> definitely nothing I'd like to see in the Core.
>
> Masi

ok, here is an official statement from the docs (see Notes)
http://php.net/en/language.basic-syntax.instruction-separation

vg  Steffen