On 03/30/2016 11:40 PM, Fons Adriaensen wrote:
> AFAIK, placing a { at the end of a line is something from
> the times when each byte would cost half a dollar.
I recently learned to use it to indicate functions or scopes (curly on
newline) vs branches. /^\t*{$/ matches declarations.
But to each his own.
> But I can live with that. But not with indentation that
> completely obfuscates code structure. I had good reason
> to modify the layout of the code where I did that, it
> was a mess to start with.
How is mixing whitespace and actual code-change in a single patch not
exactly the same kind of of obfuscation and mess? The diff is just as
unreadable as the source that was criticized for being unreadable.
ffmpeg for example drives a very hard line: not even a single no-op or
whitespace change must ever coincide with an actual code or functional
change. Personally I think that's a bit unreasonable, but it does make a
lot of sense for huge projects with countless contributors and a only a
small team to review each and every change.
2c,
robin
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user@xxxxxxxxxxxxxxxxxxxx
http://lists.linuxaudio.org/listinfo/linux-audio-user
