this post was submitted on 10 Feb 2024
221 points (100.0% liked)

196

16423 readers
1698 users here now

Be sure to follow the rule before you head out.

Rule: You must post before you leave.

^other^ ^rules^

founded 1 year ago
MODERATORS
greembow@lemmy.blahaj.zone
moss@lemmy.blahaj.zone
moss@lemmy.world
queue@beehaw.org
funky_rodent@lemmy.blahaj.zone
PeachyMcPeachface@lemmy.blahaj.zone
threegnomes@lemmy.blahaj.zone
greembow@lemmy.world
remotelove@lemmy.ca
Roflmasterbigpimp@feddit.de
qaz@lemmy.world
A_Very_Big_Fan@lemm.ee
qaz@lemmy.blahaj.zone
qaz@lemmy.ca
A_Very_Big_Fan@lemmy.world
qaz@lemmy.dbzer0.com
Qaz@lemmy.ml
qaz@sh.itjust.works
qaz@lemmy.sdf.org
221
Antimemes rule (lemmy.dbzer0.com)
submitted 8 months ago* (last edited 8 months ago) by moosetwin@lemmy.dbzer0.com to c/196@lemmy.blahaj.zone
36 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] azertyfun@sh.itjust.works 6 points 8 months ago

Every C-inspired language with curly braces (which is a lot of them) that I know uses some variation on K&R/Allman.
Golang straight up enforces the "K&R" style and doesn't recognize a curly brace on a new line. I don't know of a JSON prettifier that doesn't use "K&R" style either.

Unless you mean that the Haskell/Lisp styles make more sense in Haskell/Lisp, which, yeah, obviously. Hopefully no-one actually writes C code like that.