proposal: move C and Fortran code into separate directory/project structures

[Karl Tarbet]

I'm looking for feedback on this proposal.

It would create clarity if the code for each project had it's own directory. This would simplify makefiles, and give clarity on what project depends on what code.

current - heclib_c
-------
Dss7/Internal
Dss7/Public
Dss7/SemiPublic
Dss7/System
Dss7/Utilities
Dss7/Utilities/DateTime
DssInterface/CandFortran/C
DssInterface/v6and7/C
Dss6/C

proposed 
------------
heclib_c/src/headers
heclib_c/src/Internal
heclib_c/src/Public
heclib_c/src/SemiPublic
heclib_c/src/System
heclib_c/src/Utilities
heclib_c/src/Utilities/DateTime
heclib_c/src/DssInterface
heclib_c/src/DssInterface/v6and7
heclib_c/src/Dss6


current heclib_f 
-------
Dss6/Fortran
DssInterface/CandFortran/Fortran
DssInterface/v6and7/Fortran

proposed 
------------
heclib_f/src
heclib_f/src/DssInterface
heclib_f/src/DssInterface/v6and7

[Neema Nejad]

I like this idea, we'd just need to make sure to update all the references to those files.

[Mike Perryman]

Anything that makes it easier to understand what's going on gets a 👍 from me.

[Mike Neilson]

I like the idea. My brain goes to the following structure:

heclib/src/c/
heclib/src/fortran

But it's been changed a lot by gradle, and you're in the code more so take that suggestion with a grain of salt.