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

[Xavier Perseguers]

Hi,

> Franz Holzinger wrote:
>> Problem:
>> The EM gives information containing code warnings and naming annoyances.
>> A normal user will get frightened by such warning messages. So they will
>> send emails to the extension authors. It is not the task of the EM to
>> show this information.
>
> -1 because it is very useful for extension authors, who want to keep their
> extensions in good shape.

I agree.

>> Zeigt an, welche PHP-Klassen innerhalb von .php- oder .inc-Dateien
>> gefunden wurden.
>> Code warnings:
>> (developer-relevant)     The XCLASS filename-key
>> "ext/div2007/hooks/class.tx_div2007_hooks_cms.phpp" was different from
>> "ext/div2007/hooks/class.tx_div2007_hooks_cms.php" which it should have
>> been!
>
> Yes, it is an XCLASS error.
>
>> 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.

Cheers
Xavier