IAP GITLAB

Coding style guide needed

The wiki refers to (non existing) coding guidelines. As we are adding contributors to the project, this will become more important.

This thought got triggered when I was looking into the ordering of #include directives. I found different orders in the code.

In my experience, the order

  1. Project (corsika) headers
  2. Other
    1. Third party
    2. boost
    3. STL

is a reasonable order. By having the project headers first, you are more likely to get a compile time error if a header is missing an include.

For the discussion, we should try to get feedback from @darko as auger's chief style cosmetologist. He spent some time on the attached auger offline style guide.

image

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information