Avoid Else, Return Early (2013)

Re:Avoid Else, Return Early (2013) by lokedhs on Tuesday March 27, 2018 @09:38PM (#16694458)

I've always wonder why no C or Java code formatter tool allows me to use Lisp-style formatting. It's clearly superior, and the popularity of Python should prove that people are OK with not having closing braces on their own lines:

    void foo(int x) {
        if(x == 0) {
            bar() }}

[ Parent | on HN ]

Re:Avoid Else, Return Early (2013) by jrimbault on Wednesday March 28, 2018 @02:43AM (#16695895)

After having seen a meme, I gave a teacher a project formatted like this:

    public class Main                                        {
        public static void main(String[] args)               {
            System.out.println("Hello world!")             ;}}

We had a good laugh. (that was fine with him, of course as long as it's a joke)

PS: getting back to the original topic, imo, formatting style should be project-wide rules set at the beginning or during refactoring. Don't get too hung up on style as long as it stays consistent.

[ Parent | on HN ]

Re:Avoid Else, Return Early (2013) by kazinator on Friday March 30, 2018 @12:24AM (#16713652)

I've written a bit of code formatted rather like this:

    void foo(int x)
    { if(x == 0)
      { bar(); } }

That is workable. I have adhered to it (mostly) in this Yacc grammar file: http://www.kylheku.com/cgit/txr/tree/parser.y

Just in the grammar; not in the supporting functions.

It's an attractive style for C statements embedded in another language, because they look more like capsules somehow.

[ Parent | on HN ]