It would be good to structure the source code better.
Suggestions:
1) Put the interface headers in an include directory. This nearly all the header files I think.
2) Put (and install) the header files in their own directory. For example include/hcana/HEADER.h.
3) This leads to use cases like:
#include "hcana/THcParmList.h"
(note this doesn't have to happen in the current source code include directories can be added to compiler flags).
4) This header name space then leads to clearer class names. (Using class name prefixes is old fashioned and ignores the namespace feature of C++).
#include "hcana/ParameterList.h"
5) Clearer header file and class names leads us finally to functional separation. Perhaps by detector type: (note this is just a suggestion)
It would be good to structure the source code better.
Suggestions: 1) Put the interface headers in an include directory. This nearly all the header files I think. 2) Put (and install) the header files in their own directory. For example
include/hcana/HEADER.h
. 3) This leads to use cases like:(note this doesn't have to happen in the current source code include directories can be added to compiler flags).
4) This header name space then leads to clearer class names. (Using class name prefixes is old fashioned and ignores the namespace feature of C++).
5) Clearer header file and class names leads us finally to functional separation. Perhaps by detector type: (note this is just a suggestion)
Here is how it could look:
Again, this is just a suggestion to help others understand the code, and is common practice in C++ projects.