> I'm not a fan of that approach.
>
> * Indent rules are often overrideen when it makes sense for
> specific pieces of code.
>
> * Automatic indenters sometimes have bugs.
>
> * It's annoying to have code look different in your editor
> than what ends up in the source code repo, as I then have
> to reformat it on every checkout update as well and then how
> do I do diffs etc?
Ok, the diffs can be a pain as ignoring whitespace is usually not enough
(braces on different lines etc.). I guess the only way then is to
publish the coding style and enforce it rigorously :-)
Maybe a readymade emacs/eclipse/your-fav-ide formatter rules could be
included in the site or even in the repo?
Br,
--
perl -e '$...@=[[0,0112,0,0],[0,0101,0,0],
[0,0120,0,0],[0,0110,0,0]];$[=256/8-0x1D;
print(chr(@{$_}[+($[+1-1+1)]))for(@{...@});'
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
