Besides revising popular packs, priority could be given to revising packs that used deleted features and are no longer standard Fortran. Slatec is not, for example. A second priority is packs that use obsolescent features, even after automatic conversion to free source from the obsolescent fixed source form. For any code, two milestones would be (1) legal (2) non-obsolescent. Although work would go beyond these objectives, some conservative users who want to minimize the risk of new bugs may choose to use versions that meet these objectives, which should be accessible on GitHub
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Tips on modernizing old fortran code? | 18 | 2553 | June 8, 2023 | |
Poll: refactoring a chunk of legacy code | 56 | 2837 | February 28, 2022 | |
Resistance to modernization
|
108 | 5444 | September 7, 2022 | |
Using reserved words as variables | 61 | 2151 | September 4, 2023 | |
Why is C used in many optimization libraries? | 17 | 907 | January 30, 2022 |