I am contemplating writing a .cfg library for an open source project that I am involved with, and have read reference-cfg-format.pdf
Are there any tools to assist in developing or maintaining a .cfg library ?
These files have a lot of "boiler-plate"; does anyone have configs for an editor to simplify entering this ?
Is it cppcheck's job to inform (perhaps with --enable=style) when experimental/deprecated/obsolete APIs are used ?
How would I indicate such APIs in the .cfg library ?
Thanks,
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am contemplating writing a .cfg library for an open source project that I am involved with, and have read reference-cfg-format.pdf
Are there any tools to assist in developing or maintaining a .cfg library ?
These files have a lot of "boiler-plate"; does anyone have configs for an editor to simplify entering this ?
Is it cppcheck's job to inform (perhaps with --enable=style) when experimental/deprecated/obsolete APIs are used ?
How would I indicate such APIs in the .cfg library ?
Thanks,
See e.g. the lines starting with
<warn
in posix.cfg.cppcheck-gui
has an integrated editor for parts of the library files.