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

[Dmitry Dulepov]

Hi!

Jigal van Hemert wrote:
> I already suggested to put the checks in extdeveval, which is "A backend
> development module that offers tools to help developers evaluate, clean,
> optimize and document their PHP scripts developed for TYPO3" (as Kasper
> described it).
> Exactly the right place IMO.

It is out of date and not really maintained. The better solution would be
to have a "developer's version of TYPO3", which will include tools for devs
to validate their code. Until we have that, I do not really see other
"under hand" alternative than "EM".

May be we can make an option for EM named "Show developer's warnings"? That
would suit everybody I think.

> Well, if you insist on using that analogy: my car doesn't give me a
> detailed description in case something goes wrong. I need to get a
> mechanic with a special tool (computer) to read the engines error logs.
> He can tell me what was wrong.

Not really ;) You get several lamps: engine, gasoline and oil at least.
More complex cars may warn you about tire pressure and other stuff. So you
really get many warnings from the car :)

People often say that many extensions in TER is rubbish. Even popular
extensions are terribly coded. Personally I hope that having those reds in
EM will force devs some day to improve their code. Yes, I know, I am over
optimistic... ;)

-- 
Dmitry Dulepov
TYPO3 core&security team member
Twitter: http://twitter.com/dmitryd
Read more @ http://dmitry-dulepov.com/