That's true, so it would be more useful in C than in Go. However, please everybody stop calling it K&R style, because it is not.
On Fri, Jul 28, 2017 at 1:54 AM, John Souvestre <j...@souvestre.com> wrote: > Ø Btw here are the result of a small internet poll on indentation styles > : > > - Allman : 7450 votes > - K&R style : 5514 votes > > Ø … > > > > I have to wonder if a person’s choice of style might depend on which > language they are using. For example, I might prefer Allman while working > in C but K&R while working in Go. The deciding factor being that Go always > uses a block for if’s, while C (if memory serves) uses either a single > statement or a block. Thus, when scanning the code quickly, seeing the > opening brace doesn’t add any info to my understanding of what takes place > in Go while it would in C. > > > > John > > John Souvestre - New Orleans LA > > > > *From:* golang-nuts@googlegroups.com [mailto:golang-nuts@googlegroups.com] > *On Behalf Of *ecstatic.co...@gmail.com > *Sent:* 2017 July 27, Thu 03:33 > *To:* golang-nuts > *Cc:* yout...@z505.com > *Subject:* Re: [go-nuts] Re: No Allman-Style, No go! > > > > I don't know if you have read this post above : > > "BTW, I've just released Genesis, an open source generic preprocessor > which automatically converts Allman style code into K&R and allows > genericity by parametric instantiation. > > https://github.com/senselogic/GENESIS > > Better late than never... ;)" > > Obviously, I don't like AT ALL the K&R style, to which I prefer the Allman > style, for not only personal but also OBJECTIVE reasons. > > And yet I've learned Go and enjoy a lot to use this language, despite this > implies using an external tool to add genericity and fix the code > indentation. > > Btw here are the result of a small internet poll on indentation styles : > > - Allman : 7450 votes > - K&R style : 5514 votes > - Whitesmith : 455 > - GNU : 422 > - Horstman : 131 > - Pico : 93 > - Banner : 243 > > (http://www.terminally-incoherent.com/blog/2009/04/ > 10/the-only-correct-indent-style) > > Even if these 14000 votes are obviously not enough to reflect the whole > development community, at least you can see here that many developers > prefer the Allman style to the K&R style. > > So sorry, but I completely disagree with your advice to stay away from Go > if you don't like its forced indentation style policy. > > It's not only too radical, but also not needed, as there are already tools > to fix that issue. > > On Wednesday, July 26, 2017 at 12:01:19 AM UTC+1, JuciÊ Andrade wrote: > > I propose a new rule for our Code of Conduct: Before posting to the "No > Allman-Style, No go!" thread, you shall read and understand all previous > posts in the aforementioned thread. > > > > Justo to be clear: Go indentation style is a time saver. It was carefuly > crafted to piss some people off. As you can see, it works wonders. If > someone can't handle a simple change in indentation style, then she has no > business trying to learn Go, so she quits, thus saving time. > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "golang-nuts" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/golang-nuts/rzLzp_Z74ik/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
