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

Dmitry Dulepov dmitry at typo3.org
Mon Mar 2 14:47:44 CET 2009


Hi!

Patrick Broens wrote:
> What's the fuzz about? It does not break any extension.
> makeInstanceClassName() is only marked as deprecated, it's still
> available. We have a lot of deprecated functions in the core for
> backwards compatibility. The solution for makeInstance() is well written
> and doesn't break anything either. We need the check for t3lib_Singleton.

Patrick, do you use latest core at all? I have tons of deprecation messages in BE and FE these days. Sometimes I even not able to edit anything in BE because these messages are over the "Save" buttons. If makeInstanceClassName() is deprecated, even more messages like this will show up (including from your extensions!).

What happens if such message comes inside AJAX call? Did you think of that? Probably not...

> You don't have to rewrite anything in your extension, but when you use
> the new functionality of makeInstance(), you have to make your extension
> dependending on 4.3 >= anyway.

Ok. I will make RealURL dependent on 4.3. So if you find a bug in RealURL, forget about updates for 4.2. Agreed? :)

-- 
Dmitry Dulepov
TYPO3 core team
http://dmitry-dulepov.com/
"Sometimes they go bad. No one knows why" (Cameron, TSCC, "Dungeons&Dragons")


More information about the TYPO3-team-core mailing list