[TYPO3-core] RFC #15489: remove code warnings about XCLASS and naming annoyances

[Franz Holzinger]

Le 21/10/2010 19:54, Xavier Perseguers a écrit :
> Hi,
>>> Class filename "hooks/class.tx_div2007_hooks_eval.php" did NOT contain
>>> the class "tx_div2007_hooks_eval"!
>>
>> And this is a TYPO3 CGL error that developers should fix.
>
> Exactly! Extension authors should deliver properly-coded extensions to
> their customers. It does not cost anything to update the checksums and
> add XCLASS definition to classes. This is part of TYPO3 CGL and should
> be taken into account with the extension release cycle.
>

This is wrong. The CGL are obligatory only for TYPO3 Core and _not_ for 
extensions. So why should extension developers be forced to the CGL?

And it does not make any sense to show a warning message if the PHP code 
does not match the CGL. Most users get frightended and very confused 
when they see a code warning message. However the PHP code still works 
without any problem.
And besides you can write a PHP code which applies to the coding 
guidelines, but which contains may severe security bugs. No warning 
message would be given in this case.


- Franz