[TYPO3-core] RFC #10497: Mark t3lib_div::makeInstanceClassName() as deprecated

[Michael Stucki]

Hi Dmitry,

Dmitry Dulepov schrieb:
> Oliver Hader wrote:
>> It was you giving the veto. So please sum up the reason in short
>> here why you did that and what a suitable solution should look like
>> in your eyes. Thanks!
> 
> I did it several times in this thread :)

I will reply to the rest of your points next.

>> Besides that, I pointed out what I'd like to see before the commit:
>>  * proper handling of notices/warnings/errors (which is a general
>> thing and not related to this RFC only) - or - * possibility to
>> disable the PHP notice trigger in 
>> t3lib_div::logDeprecatedFunction()
> 
> If and when we have that all, the veto will be revoked immediately!

Which is the case now.

> The purpose of this veto is to prevent an immediate break of FE and
> BE output for many extensions. TYPO3 *must not* cause major problems
> after upgrades. The change as proposed creates those major problems.

Actually not. I've seen warnings already caused by other deprecated
function calls. It would just have raised the number of warnings once
more...

> I have seen companies that stay om 4.1 because 4.2 caused too many
> problems during migration.

If that was true we'd have a serious problem. However, I cannot find any
proof for it. If you think there is, please move the topic. It should be
discussed but not on this list.

Warm regards
- michael
-- 
Use a newsreader! Check out
http://typo3.org/community/mailing-lists/use-a-news-reader/