@falkreon My favorite was MANY years ago when I was a lot less experienced than I am now, a programmer I looked up to had an extra semicolon...
if (VeryLongFunctionName(foo, bar, smeg, head));
The condition was well past 80 characters long and no one noticed the extra ; on the end of the long line, so that next block of code always ran.
I learned a lot about programmers the day we found that.
That said, auto-indent and me tend to butt heads even when configured to my code standards (such as preemptively indenting something while I'm editing it which, when finished, won't be indented, but then not updating the line once finished). So that particular thing, I don't use.
As every tool, they shape the work, if you like mashing your spacebar more than negociating with the indent-engine, that's your call.
But having a mechanical thing trying to add redondance into the syntax can only help to see what you've truely written (instead of what you would like to have written)
@webshinra I prefer not to lisp, honestly. It's in the same category as regexes: Not verbose enough to ever be clear, no matter how careful you are.
@falkreon Do as you wish, but I was speaking of the tool, which is conceptually interesting to understand as a programmer.
(But notice that's probably not a really pertinent critics, expressibility being the main advantage of sexp syntax. Maybe learning scheme or whatever modern lisp correctly could help understand that.)
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!