[TYPO3-core] RFC #15489: remove code warnings about XCLASS and naming annoyances
Jigal van Hemert
jigal at xs4all.nl
Thu Nov 11 22:16:50 CET 2010
Hi,
Generalizations are dangerous...
On 10-11-2010 16:22, Franz Holzinger wrote:
> If an extension is based on XCLASS, then this is not a good solution.
DBAL is based on XCLASS :-)
> XCLASS will lead to errors because the original extension will not care
> about the derived extensions using the XLCASS. A good code will only
> base on a hook function.
If there are no hooks available you're stuck with XCLASSes. Some XCLASS
implementations are quite 'solid'. E.g. the new version starts or ends
with a call to the parent.
> The XCLASS warning is not important to anyone, not even to developers.
Well, the XCLASS warning is not about the code relying on another class
by XCLASSing that other class, it's about a missing or incorrect XCLASS
"footer".
This is relevant to the developer (maybe a typo?). But IMO it is not
relevant for the EM (but others disagree on this).
--
Kind regards / met vriendelijke groet,
Jigal van Hemert
skype:jigal.van.hemert
msn: jigal at xs4all.nl
http://twitter.com/jigalvh
More information about the TYPO3-team-core
mailing list