-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warnings for undocumented entities: feature request #25
Comments
I've added this feature and pushed it to the Github repository. I don't plan to put out a new release for it (yet) though, as I'd prefer to have more than just one new feature before I do that (some bugfixes at least). The command-line syntax is -w or --warn to produce the warning messages. Alternatively, placing "warn: " in your project meta-data will do the same thing, so long as some character follows the colon. Unfortunately, there is no easy way to allow it to provide a line number (sorry about that, I realize it would have been useful). Maybe a feature for some other time. |
Great Chris. Don't worry about line number, the warn on name of entity is enough! I will try it late in the morning. Thanks. |
Just tested... works great! But there is something that is not well documented... Let us consider IR_Precision module. The latest ford in warn mode tell me ...
Warning: Undocumented variable MinR16P in file IR_Precision.f90
... As you can see here the variable is really not documented by Ford, but it has its "own" docstring, see this line 98. I guess that the problem is due to my bad attitude to use one docstring for more than one variables (that are grouped being similar in some ways). As a matter of fact, line 98 defines two variables, namely I suppose that it is very difficult to allow many variables sharing the same docstring, this is just a remainder. Thank you very much for great work. |
This is intended behaviour. When multiple variables are declared on one On 27/01/15 06:41 AM, Stefano Zaghi wrote:
Chris MacMackin |
Sure, I agree with you. This is just a remark for eventual, future improvement. Thank you again. |
Hi Chris, I have found a possible "false" positive warning. In FLAP the type bound procedures (e.g. free or check) have their own docstring (e.g. see free one). However, Ford complains with them giving me: |stefano@zaghi|0|02:26 PM Tue Jan 27|
|~/fortran/FLAP|10 files, 92Kb|
|->~/python/ford/ford.py -w doc/main_page.md
Reading file ./src/IR_Precision.f90
Reading file ./src/flap_test.f90
Reading file ./src/Lib_Strings.f90
Reading file ./src/Data_Type_Command_Line_Interface.f90
Reading file ./src/Lib_IO_Misc.f90
Warning: Undocumented boundprocedure free in file Data_Type_Command_Line_Interface.f90
Warning: Undocumented boundprocedure check in file Data_Type_Command_Line_Interface.f90
... Have I done a mistake in documenting the type bound procedure, line 701? |
Okay, this is actually fairly subtle. For bound procedures and module On 27/01/15 09:36 AM, Stefano Zaghi wrote:
Chris MacMackin |
Ok, now it is more clear. The warnings disappear if the type bound procedure have their own docstrings also into the Thank you Chris. |
Hi Chirs,
During the porting of all my other Fortran codes from doxygen to Ford I have realized that it would be a very nice feature to have the possibility to activate a "verbose checking" that will advice for entities that Ford has recognized without a documentation. As an example,
ford -warnall ...
prompting to stdout something like paranoiac advice for undocumented entities.file bar.f90
Ford paranoiac mode
The text was updated successfully, but these errors were encountered: