[rkward-devel] indentation conventions
thomas.friedrichsmeier at ruhr-uni-bochum.de
Thu Dec 18 13:27:30 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 18 Dec 2014 11:35:53 +0100
meik michalke <meik.michalke at uni-duesseldorf.de> wrote:
> so far we seem to use tabs for indentation of code. for kdelibs, 4
> spaces instead of one tab is recommended:
> the same seems to apply for R code (though 2 spaces are also fine):
> is this something we should care about?
For KDE, different projects use different styles, already (and tabs vs.
space are not the only style-question, of course). I'm not particularly
attached to the style we're using, but changing styles is always
somewhat problematic. Importantly, git blame will stop on such changes,
even if the code is otherwise untouched. (Arguably, git gui blame is
comfortable enough to live with this). Either way, I'd vote against
changing this, unless there are compelling reasons, _and_ a very clear
definition of what the new style should be.
For R, the case may in fact be somewhat different, esp. as the
recommended style is also what you get from deparsing / printing R
functions. Not sure, whether it would be possible to use "astyle" to
convert package code, automatically. Adjusting plugin generated code
would probably require some manual work. Sure, tabs can simply be
replaced, but perhaps there are some - few - instances of tabs worth
keeping (inside strings, for example)?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
More information about the Rkward-devel