[TASK] Deprecate callUserFunction "&" token for persistent objects 93/50693/6
authorBenni Mack <benni@typo3.org>
Thu, 17 Nov 2016 11:04:16 +0000 (12:04 +0100)
committerOliver Hader <oliver.hader@typo3.org>
Thu, 1 Dec 2016 17:27:46 +0000 (18:27 +0100)
commited46dc43ff4e784bb51c233e4cf6fb79b717315f
tree5360f5902ffde9cb273784a2d7db8a964a30c92e
parentc0e83fc8ad2db4aef08108b6b16841741963b60c
[TASK] Deprecate callUserFunction "&" token for persistent objects

The method GeneralUtility::callUserFunction() method allows
to call "&" to put this logic into a "persistent" pool. We already
have the SingletonInterface which should be used for objects
that should be persistent.

Currently there are two "persistent object pools", one for
makeInstance and one for callUserFunc, which makes it very hard
to understand which object is used when. Reducing complexity
and using the SingletonInterface everywhere should be the best practice.

Resolves: #78733
Releases: master
Change-Id: I6d3c57056c2b5ab411a9b9f488dc48c757b4a148
Reviewed-on: https://review.typo3.org/50693
Reviewed-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: Oliver Hader <oliver.hader@typo3.org>
Tested-by: TYPO3com <no-reply@typo3.com>
typo3/sysext/core/Classes/Utility/GeneralUtility.php
typo3/sysext/core/Documentation/Changelog/master/Deprecation-78733-CallUserFunctionTokenForSingletonObjects.rst [new file with mode: 0644]