Re:John Carmack's comment on Doom 3's code style
by npsimons on Monday January 14, 2013 @06:00PM
(#5057231)
It's funny you mention that, as I'm using the companion program (http://google-styleguide.googlecode.com/svn/trunk/cpplint/cp...) on the code for my current project right now. My only complaints is that much of the cpplint program checks for arbitrary style choice versus possible issues. Sure, most of the style I agree with, but I've actually hacked on that program a bit because the style guidelines are hardcoded in it. I'm halfway tempted to make it more flexible in terms of style, or at least separate the style components from the linting parts.
[ Parent
| on HN ]
Re:John Carmack's comment on Doom 3's code style
by nostrademons on Monday January 14, 2013 @06:15PM
(#5057319)
That's my pet peeve about many linters as well - I don't use jslint because it has many of Crockford's personal style tastes embedded in it, several of which I disagree with. In cpplint's (and perhaps jslint's) defense, it was written for one specific organization with broadly-accepted style guidelines, and open-sourced "in the hopes that it'll be useful, but without any warranty of any kind".
Re:John Carmack's comment on Doom 3's code style
by esrauch on Monday January 14, 2013 @07:24PM
(#5057627)
jshint was started in part to separate out the actual warnings from Crockford's style in jslint (it is also supposed to be more configurable with regards to style-type comments). It might be worth a look if that is the only reason you disliked jslint.