[TYPO3-core] RFC #12272: Steps disregarded in t3lib_lock

[Christian Kuhn]

Hey,

Martin Kutschker wrote:
>> Unfortunately we cannot since the variable is protected and not private
>> and we have a XCLASS definition in that t3lib_lock. Thus, an extension
>> could override the original behaviour but rely on $this->step - even if
>> the name is not nice.
> 
> The idea was that all protected methods and properties are subject to change. An XCLASS is only a
> helper to ease hacking not a contract. If we cannot change protected methods and properties for the
> sake of XCLASSes we can drop the "protected" declaration right away.

That's my feeling, too. I think we should be able to rename protected 
vars, at least between major versions. XCLASS'ing something might always 
break (because of method or logic change) and needs to be maintained 
anyway by the extension author. I bet half of the XCLASS extensions 
working in 4.2 are broken in 4.3, that's one of the reasons why we want 
better object abstraction and hooks.

Regards
Christian