Skip to content
Chris MacMackin edited this page Apr 26, 2015 · 15 revisions

This software is still extremely young and much remains to be done. Various things which I'd like to do at some point include:

  • Support some of the old Fortran 77 ways of doing things, as these are often still used. This includes PARAMETER statements and EXTERNAL statements. Support for fixed-form code is less of a priority.
  • Add the ability to produce dependency diagrams and inheritance diagrams for modules and types, respectively.
  • Make more options configurable from the command-line.
  • Test on some more code, including that of other people, who may have different coding styles.
  • Add the ability to identify function calls and use this to work out call-trees (subroutine calls are already captured, although not yet used in any of the output).
  • Add the option for users to specify a Creative Commons license for their documentation, which will be inserted into the page footer.
  • Make it possible to override the display options within a particular part of the code and/or for an individual item within the code.
  • Provide an option to force all (non-string) text which is captured to be lower case.
  • Add the ability to recognize the use of intrinsic modules
  • Add the ability to allow for only statements when loading modules and for renaming module procedures when loading them.
  • Improve the sidebar for source files so that it will link to the items that it lists.

Things which ideally I would do, but are not currently on the radar include:

  • Add the ability for people to customize appearance of the output more (this would require drastic changes to the template system).
  • Support fixed-form Fortran (doable, but low priority).
  • Add the ability to identify type-bound procedure calls and use these to construct call-trees. This would be extremely difficult, as it would require keeping track of names and types of variables throughout the code.
Clone this wiki locally