News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Volker Dusch:
Errors will be fixed. Warnings will be 'looked at'
October 04, 2012 @ 08:25:43

In a new post to his site Volker Dusch shares his thoughts about warnings in coding style checks (and how they differ from real errors).

When it comes to coding standards there is one rule that always makes me cringe when I stumble upon it: "Lines SHOULD be less than 120 chars long. If not a warning will be issued." Let me try to make a point why I consider WARNINGS in coding guideline checks hurtful.

He defines a warning first, so there's no confusion (something that should be done, but doesn't have to) and why he thinks there's not much of a place for them in the code guidelines. He suggests that, by having them, they take away time from the real issues, the errors. He notes that "should" rules on formatting shouldn't be added to your QA tools right away. Adding too many of these that spit out too many warnings (not errors) could just muddy the waters and make the developers more confused.

0 comments voice your opinion now!
errors warnings qa code style guidelines opinion


blog comments powered by Disqus

Similar Posts

Vance Lucas' Blog: NoSQL First Impressions: Object Databases Missed the Boat

Paul Reinheimer's Blog: Memcached Constants - Lame Code

Lee Davis: Is a HTTP DELETE request idempotent?

Slava Vishnyakov: PHP the Nice Way (Ever-evolving Huge Retailer Website Story)

php|architect: Programming: you’re doing it wrong


Community Events





Don't see your event here?
Let us know!


interview zendserver laravel podcast conference list series introduction symfony library framework community api voicesoftheelephpant developer bugfix deployment language tips release

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework