IAP GITLAB

Update Coding Conventions and Guidelines authored by Ralf Ulrich's avatar Ralf Ulrich
...@@ -7,8 +7,10 @@ NOTE: please carefully evaluate and give feedback. ...@@ -7,8 +7,10 @@ NOTE: please carefully evaluate and give feedback.
# Project structure # Project structure
The CORSIKA8 structure is set up following the guidance of other large software projects: The CORSIKA8 structure is set up following the guidance of other large software projects:
- boost, e.g. https://github.com/boostorg/histogram --> very similar project structure - boost, https://github.com/boostorg --> very similar project structure
- ranges-v3, https://github.com/ericniebler/range-v3/tree/master/include/range/v3 --> very similar project structure
- NVIDIA/thrust: https://github.com/NVIDIA/thrust --> the use of ```*.inl``` files - NVIDIA/thrust: https://github.com/NVIDIA/thrust --> the use of ```*.inl``` files
- EvtGen, https://phab.hepforge.org/source/evtgen/browse/master --> similar class (etc) naming conventions
Advantages of this structure are: Advantages of this structure are:
- clear correspondence and traceability of files/locations, in particular if they are ```#include```d - clear correspondence and traceability of files/locations, in particular if they are ```#include```d
... ...
......