Closed beserge closed 4 years ago
Update the documentation so that it matches doxygen formatting (interestingly this won't register as being documented, and therefore won't throw errors).
check through some of the other files for syntax as necessary, but pretty much
/** Description
Any other details
\param foo array
\param size number of elements in foo or whatever
\return a magic spell designed by foo runes
*/
magic_spell create_spell(void* foo, size_t size);
We should eventually enable WARN_AS_ERROR
in the doxyfile. Then the check will fail on undocumented code. I had left this off because it would have made the transition to doxygen quite painful.
ATM there are a few other warnings that will have to be resolved before we can turn WARN_AS_ERROR
on.
@TheSlowGrowth yeah, I figured there was a setting for that in the Doxyfile.
On my dev machines I don't get any warnings from rebuilding docs, but I do see warnings on the CI. Mostly for invalid keys (which I'm guessing is a version discrepancy).
Might sound a bit better with a slower LFO, but no more pop. So that's good.
Brought up to speed with master.