- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This also has some bearing on the interface discussion we are currently having.
If I am calling a routine and make changes to the interface (type of arguments, order, or number),
then how can I guarantee that the called routine gets compiled FIRST?
If I do a clean and rebuild, I need to do that so that the changes in the interface are noted BEFORE
a calling routine gets compiled. Otherwise it generates a lot of compilation errors even if I have already
made the appropriate changes to the calling routines.
One way around this problem is to have the project scanned first to assure that called routines (lowest on the tree)
gets compiled first.
If I am calling a routine and make changes to the interface (type of arguments, order, or number),
then how can I guarantee that the called routine gets compiled FIRST?
If I do a clean and rebuild, I need to do that so that the changes in the interface are noted BEFORE
a calling routine gets compiled. Otherwise it generates a lot of compilation errors even if I have already
made the appropriate changes to the calling routines.
One way around this problem is to have the project scanned first to assure that called routines (lowest on the tree)
gets compiled first.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can't, unfortunately. The build system does not take generated interface checking into account. However, if you adopt modern Fortran programming practices and have all your routines in modules, then you'll get the benefits of the checking and the build order will be automatic.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page