[TYPO3-dev] t3lib_div - why final ?

[Stefan Geith]

Michael Stucki schrieb:
> Hi Stefan,
> 
>>>> just a question: why must t3lib_div be final ?
>>> I doesn't support XCLASSing and it is not meant to be a private
>>> playground.
>> Sure, it does not support XCLASSing,
>> but if someone extends t3lib_div (or t3lib_extmgm), he
>> will get errors now in 4.2 - so it breaks compatibility
>> for my/some plugins ... :(
>>
>> As there is no way to XLASS t3lib_div, why should extending
>> be restricted ? I only can use this extended t3lib_div-derivate
>> in my own plugins - so this should not be a problem for Typo3.
>>
>> So _please_ remove the final form t3lib_div, t3lib_extmgm and
>> all other not XCLASSable classes in t3lib.
> 
> I agree with Masi and Dmitry, there seems to be no need to extend t3lib_div.

Looked from the other side, you could also say:
There seems to be no need to make t3lib_div final.


> Can you quickly explain how and why you want to do this?

I use this in development.
I wanted to have one single class that handles all
these little helpers as t3lib_div does; so I extended it.
For testing, I sometimes modified existing function
to contain debug-statements without disturbing the core
and/or other extension, that use the original t3lib_div.

There might be other applications, where it is usefull
to extend t3lib-classes; maybe for testing / developpment etc...

I simply don't want to have 'the door locked'...

Can you give me an example, why it would be better to
have t3lib-classes to be final ?
They don't provide XLASSing, so there is no risk for
the core nor for existing plugins ... right ?

--

Stefan