Re: compilation cascades and new Fortran features
On 2005-09-29 22:36:04 -0300, robert.corbett@xxxxxxx said:
Now, I am wondering if some the new features introduced in
F2003 bring new solutions for that problem ? Could you
comment on that ?
No. Make is not capable of handling the usual implementation of
Fortran modules without either missing some necessary rebuilds
or doing some extra rebuilds. Make could be extended to deal
with Fortran modules, but I don't know of work being done along
those lines.
Bob Corbett
The MacOs (not the MacOsX based on Unix) had a developer environment
that was command line based and looked much like Unix in many repsects
but also paid attention to the multiple windows etc. It was MPW for
Macintosh Programmers Workbench and was an interesting hybrid.
MacOs files have both data and resource forks so the MPW version of
make had to know how to keep track of two outputs and make sure
they got pasted together etc. The problem sould seem to be a kissing
cousin of the object/module problem of F90. There was a layer of
extra fuss that did not seem excessive for the problem being solved.
The MPW make would be an interesting lesson to look at to see how
a different group solved and similar problem. Unfortunately MPW is
fast receding into the dust of history as MacOs now lives as Classic
under MacOsX and will not be present under the soon to be MacTel MacOsX.
MacOsX uses a package notion so the issues do not arise for Xcode,
their new developer environment. A package is a directory that can
inform the system that it and its contents are to be treated as a
unit and displayed as it they were a file unless the contents are
explicitly requested. They have now even taught the command line in
Unix to follow the same conventions as the GUI on this issue.
.
