Re:An Open Letter to JavaScript Leaders Regarding Semicolons
by pdw on Monday December 20, 2010 @02:05PM
(#2025349)
I do that sometimes (obviously not in JavaScript), to split up long lines in situations such as this:
I don't think that's very horrible.
[ Parent
| on HN ]
Re:An Open Letter to JavaScript Leaders Regarding Semicolons
by BrandonM on Monday December 20, 2010 @03:26PM
(#2025651)
I would tend to write that:
bool is_foo_possible() {
return test_first_condition()
&& test_second_contition()
&& test_third_condition()
}
I prefer to put my infix operators at the beginning of continuation lines, because that makes it immediately clear from a glance that it's a continuation line.
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.