You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MatthewHambley edited this page Jan 13, 2020
·
6 revisions
Motivation
In the past we have used text based tools and there's a surprising amount you
can do with regular expressions. However once context becomes important they
can become a liability. In those cases it is much better to have the parse
tree.
At the moment the tool is only able to flag up where a style rule has been
broken. For some things this is the best we can hope for but for others
we might aspire to correct the problem.
For instance the current check for missing implicit none statements might,
in the future, insert them where they are missing.
Design
Some UML class diagrams have been prepared which may be found in the
documentation directory. These make use of the
PlantUML tool to render.
PEP8 tool which makes use of pycodestyle, thus allowing Python to be handled as well. What to do about files which don't have an extension?