[TYPO3-core] "breaking" changes in minor releases?

Martin Kutschker masi-2o12 at typo3.org
Tue Jul 22 16:51:41 CEST 2014

Am 20.07.2014 23:41, schrieb Jigal van Hemert:
> Hi,
> On 20-7-2014 18:47, Helmut Hummel wrote:
>> https://review.typo3.org/20026
>> This might break hooks/ XCLASSes, as a public property is removed
> This is a harder case. The public property was "public" because it
> previously didn't have a visibility. There is a comment that it's
> internal and that the visibility had to be defined. Programmers could
> expect that it wouldn't be public in the near future.

"@todo Define visibility" makes it clear. No change for 6.2.

The hard way would be to make it protected and implementer a magic 
getter/setter that issues a deprectation warning. But it would be quite 
tedious to all those properties without defined visibility in the Core.


More information about the TYPO3-team-core mailing list