[TYPO3-core] Backporting Hooks

[Kay Strobach]

Hello Jigal,

>>>   - Having hooks backported reduces the use of XClasses
>>>     (which should be denied in my opinion)
> 
> True. (You want XCLASSes entirely removed??)

-> Xclassing is nice for small fixes or improvements, but they are also
problematic due to their limitations :D

>>>   - Having Hooks instead of XClasses reduces headaches between version
>>>     switches
> 
> Well, it adds some headaches if you introduce them in bugfix releases.
> How would you handle compatibility with 4.5.21 or higher in the 4.5
> branch, 4.6.7 or higher for the 4.6 branch, etc. It's impossible to set
> that in the dependency settings.
> 

-> You can handle that in the manual, or in the release notes of an
extension, or in an update script or in a custom field in
ext_conf_template.txt, this way it can be communicated.

Normal installations have a high patchlevel upgrade rate (atleast mine),
so it should not be a real problem, especially as these cases should be
hopefully seldom.

>>>   - Hooks usually do not break anything, but offer more possibilities :D
>>>   - Having Hooks backported atleast one version / LTS makes it easier to
>>>     make futureproof extensions
> 
> I think you mean that not using an XCLASS would make it more likely that
> it would work with a next version?

-> yes, and you avoid xclass collisions :D

> There are advantages to backporting them, but the main problem (besides
> the rule of no features in backports) is that compatibility with certain
> versions is hard to communicate.
> 

-> see above

Thanks for taking care
Kay

-- 
http://www.kay-strobach.de - Open Source Rocks

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

Answer was useful - feel free to donate:
  -
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=KPM9NAV73VDF2
  - https://flattr.com/profile/kaystrobach