[TYPO3-core] Adding visibility to methods and variables within t3lib_tcemain?

Christian Kuhn lolli at schwarzbu.ch
Thu Jun 14 21:29:01 CEST 2012


Hey,

On 06/14/2012 09:18 PM, Xavier Perseguers wrote:
>> Currently, I'm still undecided if we can realistically take this path, I
>> hope we get real opinions from more devs in this area! I tend to think
>> that we can reduce visibility for 6.0, but I also fear a shit storm if
>> we do not manage to do it in a sane way.
>
> The best way (but with possibly quite some overhead) would be to
> *deprecate* public access to methods that we want to become protected.
> This way we can then actually really "break things" in 6.2 and this lets
> us find solution or change our mind if one method really needs to be
> kept public.

That leads to lots of wrapper methods and will work (extract code part 
to protected method, deprecate old method and call the protected one). 
Problems:
- It uglifies code at least for some time.
- Proper naming might be funny, too.
- All usages in the according core code must then be reworked to the new 
(protected) method.
- It is a lot of work if we do this for significant parts of the core code.


> Perhaps we could find some clever way of doing so for members as well
> but I doubt it.

Yes, properties are more trouble.


Regards
Christian


More information about the TYPO3-team-core mailing list