[TYPO3-core] [TYPO3-core-internal] Deprecation strategy

[Robert Lemke]

Hi Ingmar,

On 08.07.2012, at 13:07, Ingmar Schlecht <ingmar at typo3.org> wrote:

> * What are the benefits of the removal (e.g. does the removal make maintenance of the code drastically easier, or is it basically no problem to leave an old method in place)
> 
> * How frequently is a method used, e.g. in extensions. How many extensions will break.
> 
> As particular striking examples for very frequently used methods, I would name t3lib_div::intInRange() and t3lib_div::readLLXMLfile().
> 
> Of course we need to keep code maintainable. However, I think the fact that TYPO3's core code is at some points rather hard to maintain is mainly due to the very complex parts like TCEMain / TCEForms or the FE bootstrapping (which is now improving), and not so much because of t3lib_div containing a few more methods than would be desirable.
> 
> So, in short, I would be glad if we could consider the impact of such method removals and weigh it against the benefits.


I agree and take it as a reminder for how we should tackle this in FLOW3 in the future. It is appealing to get the code base as clean as possible, but what counts in the end is if the users are happy …

Cheers,
Robert

-- 
Robert Lemke
Lead Developer TYPO3 Phoenix and FLOW3
Co-Founder TYPO3 Association

Blog: robertlemke.de/blog
Get involved: typo3.org – flow3.org



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2263 bytes
Desc: not available
URL: <http://lists.typo3.org/pipermail/typo3-team-core/attachments/20120710/3fa6154e/attachment.bin>