Working on porting on a fairly large computational library from FORTRAN 77 (and some FORTRAN IV to 66) to modern Fortran. By large I mean by my standards: ~250 subroutines and functions in total; ~25 APIs (exported routines from the DLL), hence many internal procedures; ~600 variables currently in COMMON blocks; roughly 350,000 lines of code.
And I could really, really use SUBMODULEs in my attempt to modularize this code. As I restructure the code, especially the internal procedures and the data they process, I realize SUBMODULEs is the main feature from Fortran 2008 standard that I miss the most. I do so for two reasons:
a) my organization insists on one procedure per file
b) as Dr. Fortran prescribes, I really prefer NOT to setup interfaces for internal routines if I can avoid them. This is especially so because Fortran routines cannot self-reference the interfaces and all the maintenance issues that go with this limitation.
Given this, my current approach is to implement "stub" routines under CONTAINS section in modules that then call actual procedures which are external but which have the same interface. And my eventual plan is to write some script (PERL, etc.) that cleans this all up when SUBMODULEs finally become available.
Any one have a better idea for a short-term solution to my needs?
I know Intel doesn't like to share details ahead of time for their future upgrades. Plus SUBMODULEs do appear to be a major enhancement, probably a significant rewrite of their compiler code. Still can anyone from the Intel staff, Steve etc., shed some light on how this feature is viewed whether it is high (or low) on the agenda, actively working (or on the backburner) etc.?