News for hackers. Stuff that matters.
Re:An Open Letter to JavaScript Leaders Regarding Semicolons by IsaacSchlueter on Monday December 20, 2010 @07:33PM (#2026401)
I do this as well.

For a while, I tried to stick to the rule that "return\n" was not allowed. When I meant to return undefined, I'd write "return undefined".

In the end, I abandoned that rule, because too many of my functions return undefined. But it's kind of a nice thing. When I do get around to building that linter, I might make `return\s*\n` verboten.

Re:An Open Letter to JavaScript Leaders Regarding Semicolons by olavk on Sunday January 02, 2011 @06:42AM (#2059893)
You could just write "return;", that would make it obvious that no value is returned.