Know what else would have spotted that error? A javascript implementation. The first time you run that code, v8 would spit out an error and give you the exact line number before it's even finished parsing. What's the point of a linter there?
Aside from that, obviously the commas at the end really *do* stick out like a sore thumb if you do comma-first style. On Feb 23, 1:29 pm, Dean Landolt <d...@deanlandolt.com> wrote: > On Thu, Feb 23, 2012 at 4:44 AM, Arnout Kazemier <i...@3rd-eden.com> wrote: > > Comma first solves that perfectly, no need to jshint that ;D > > I wouldn't say *perfectly*. There's a gaping hole in the comma-first style: > > var arr = [ "foo", > , "bar", > , "baz" > ] > > Did you spot the error right away? Neither did Brendan Eich. But a linter > would have. > > If anything this little deficiency in comma-first demands a linter. -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
