#48 Refactoring Command Line Options out of Driver into Library
[...] the driver is getting a bit polluted now. I’d like to push some of the logic inside the large command line SELECT CASE back into the layers that are being tickled. To that end, it may be useful to put FTL into pFUnit, though there are serious concerns about circular dependencies in terms of software development. (Not compilation.) -- Tom
Maybe the worry about circular dependencies (in development) is suggesting a higher level framework or concept into which both FTL and pFUnit fit. Testing and source-code control on the higher level framework might break (or manage) the circularity. One might argue this just moves the circularity: i.e. do components explicitly depend on the framework? -- Mike
In theory, clean development processes would allow this all to work. The FTL inside PFUNIT would be untouchable, except to import a new version. But even then, there would be some CMAKE weirdness.
I’m sure we’re not the 1st to face this, but I may be the most ardent in terms of wanting to make my layers seem isolated to increase the likelihood that someone will try them. Otherwise, I’d be tempted to create a generic FortranUtils project. -- Tom