Style guide and lint

[Kristoffer Gryte]

Hi,

How do you enforce the DUNE c++ style guide? Do you use some sort of linter? We are looking into setting up some CI for our repositories, to reduce the load on the maintainers, and have considered including linting in this. From the travis/appveyor config files it seems that you do not do this in the CI. My hope was that if you are using some type of linter/formater, we could save some time in configuring it to comply with the style guide. I notice that some of the available linters have a few style guide standards (LLVM, Google, Chromium, Mozilla, WebKit) that one can base lint configuration on. Is the DUNE style guide derived from any such standards?

I do not have any experience with linters, but it seems very useful and straightforward, based on e.g. this blog post.

Regards,

Kristoffer

[José Braga]

Hi,

The DUNE style was really enforced a few years ago, there would be no merge commit without the style being properly revised and during that time all developers were sort strict with it.

Looking at more recent commits that does not seem to be the case, but:

Personally, I use emacs to program and there's a init file syntax in the 'doc' folder available. There's another for Eclipse.

Someone in the past wrote one for Sublime although if I remember there was still an issue with getting the braces properly for switch cases..

Kind Regards,

José Braga

____________________

jbr...@oceanscan-mst.com

www.oceanscan-mst.com

--
www.github.com/LSTS/
www.lsts.pt
---
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchai...@googlegroups.com.
Visit this group at https://groups.google.com/group/lsts-toolchain.
To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/1048e6d0-8736-476a-b9e2-5bfe028c1bf4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Kristoffer Gryte]

Thanks José. I'll look into the files in the doc folder. My concern is mostly with code from everybody else (in merges), since it is difficult/time consuming to see if they comply with the guidelines. I'll look into the opportunities for using a linter on our next hacking day or when my mind needs a break, and I'll of course post any progress in case you want to implement something similar.

Regards,

Kristoffer