Directory structure in analysis code and build system
Hi @npostiau, @hanwen, @lyuan,
Assuming that we agree on the refactoring of the analysis code (#40 (closed)), I will be shuffling pieces of code across different files, which will break per-file history. We can use this opportunity to revisit the directory structure. What I would do is to collect all C++ files (meaning the content of directories Loopers_Includes
, Loopers_Sources
, Common
, as well as files Tools/ArgParser.*
) and move them into new directories include
and src
, as it's done usually. This will not affect .C
scripts. Do you have any objections to this? Sometimes people also add a subdirectory with the package name inside include
, so that our headers would be included like
#include <HZZ2l2nu/EwkCorrections.h>
but I think this is more appropriate for big libraries.
On a related note, I would like to upgrade the build system to CMake. Among other things, it will help with #18 (closed). I believe this is an uncontroversial improvement, but still speak up if you have other considerations.