-
Notifications
You must be signed in to change notification settings - Fork 262
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
Documentation issue: API reference does not cover all public NetCDF functions #253
Comments
Hi! Sorry for the delayed response, I've been out of the office. A pull request would be great, thank you very much! If this is no longer on your radar due to the delay, I understand, let me know and I'll look into it myself. |
This is really the same as issue: Some netcdf functions are not in the doxygen documentation on-line. #277 I agree with Constantine Khroulev that all public netCDF functions should be fully documented. I will go further and say that all private, internal functions should be fully documented. (Doxygen has the ability to build them for developers but not for users.) I suggest that you adopt this as a general principal and start checking for it in all changed code. I'm sure users would be willing to document functions in code where they are making significant changes. I know I would be happy to do so. I have not taken a good look recently at the state of documentation in netCDF internal code. Perhaps you already maintain this standard. What I am really suggesting is that you turn on doxygen warnings, get the warning count down to 0, and they have Doxygen warnings treated as errors by your automated testing. |
Running doxygen with the warning enabled turns up some surprising undocumented functions. Here the relevant warnings for public functions:
There are also hundreds of warnings for internal functions. I will see if I can knock some off documentation for some of the public functions over the next few weeks as I work on the code. |
I believe that when all current PRs are merged, this ticket can be re-evaluated to see what public functions are still undocumented. |
@WardF this issue can be closed. All public functions have documentation now. |
Please consider adding doxygen comment stubs to all functions in NetCDF's public API. This will greatly help with API discoverability even if a function's documentation is empty or just contains a "FIX ME" note.
For example: it took me a while to convince myself that NetCDF does expose HDF5's chunking settings:
nc_def_var_chunking
is not mentioned in NetCDF API reference.As a suggestion: setting
in
docs/Doxyfile.in
would produce warnings for all undocumented functions (both public and internal). Comparing these to contents ofnetcdf.h
would give a list of undocumented public functions.Let me know if I should do this and submit a pull request. (I should have some time over the weekend and I think I can automate this.)
The text was updated successfully, but these errors were encountered: