Waldek Hebisch wrote:
... snip ...
By the way, you wrote about `--include' option and the Chief suggested putting `{$incude ...}' directive in the interface. Both IMHO defeat the purpose of separate interface, as effectively interface and implementation are compiled jointly (only disk storage is separate).
I agree about no $includes etc. Believe it or not I am trying to be constructive. To me a set of sources should be able to hold nothing more than ISO standard constructs, which means no special directives, peculiar comments, etc. etc. and a straight forward and immediately understandable set of compilation commands should be available. One command option may mean "compile interface module", another "compile implementation module", much as options to gcc now say "extract dependencies" or "generate assembly source" or "generate object code" FROM A SINGLE source. The complexities arise when multiple sources need to be compiled.
I think Frank (and possibly you) is/are much too close to the actual implementation. This makes you think in terms of --automake and gp, rather than a simplified approach. Old fashioned data flow charts, in the spirit of Yourdon, may be worth while. Of coarse you (collectively) are doing the work, which certainly entitles you to choose the methodology. And I may be totally ignorant of what is really existant, and thus blathering into the wind.