Open ugeorge opened 6 years ago
Here comes a first proposal for restructuring the library for major release 4.0.0. It will suffer more drastic changes, started since 3.2.0. In principle ForSyDe.Shallow
will only export two sub-modules Core
, which contains the core types described by the ForSyDe formal framework, and MoC
which represent the MoC libraries. The rest should be considered utilities. How they are organized though, is rather tricky, due to strange inter-dependencies. I have started a wiki page and I invite the main contributors to participate to that discussion (if interested).
There are plenty of experimental modules which nobody has looked at in a long while, and do not belong to the modeling environment. Some of them might be transferred to forsyde-shallow-examples, others might be kept as utilities.
Action points
[ ] decide what to do with each module and its exported functions
[ ] perform the cleanup