[TYPO3-core] RFC #9533: substituteMarkerArrayCached is too strict for older extensions
Ingo Renner
ingo at typo3.org
Mon Oct 13 19:29:21 CEST 2008
Ernesto Baschny [cron IT] wrote:
> Ingo Renner wrote: on 13.10.2008 17:34:
>
>>> Issue was introduced almost "silently" in Bug#9283 (rev 4129
>>> http://forge.typo3.org/repositories/revision/typo3v4-core/4129) as a
>>> "cleanup" by Ingo.
>> where was this silent? It was a RFC like this.
>
> Never in the description or even in the ChangeLog we have had the
> information about that rather "crucial" change, as we have noted. A
> "cleanup" generally doesn't break things, not even badly coded extensions.
>
> The subject of your change was "declare marker handling functions of
> t3lib_parsehtml static". The bug tracker issue has just one side note
> about the change in the function of this issue:
>
> "There's also some cleanup in t3lib_parsehtml and tslib_content. No
> functionality has been changed except for the addition of the new method
> in t3lib_parsehtml".
>
> To me this is a "silent change" of functionality. I am not stating that
> you did that with bad intensions, but I think it slipped through
> unnoticed because its consequences weren't apparent.
well it was an RFC, it got +1s, all fine, right ;)
Ingo
--
Ingo Renner
TYPO3 Core Developer, Release Manager TYPO3 4.2
More information about the TYPO3-team-core
mailing list