Hello,
Just wanted to follow up on this. We found the bug (a single missing character
in a regex). A PR has been opened on github
https://github.com/doxygen/doxygen/pull/7192
Cheers,
Ryan
On Thu, 31 Jan 2019, Ryan S. Elliott wrote:
Hi Travis,
Thanks for your reply! This all sounds rea
Hi Travis,
Thanks for your reply! This all sounds reasonable. I won't be able to dig-in
to this right away, but I'll put it on my list to get back to soon.
Thanks,
Ryan
On Thu, 31 Jan 2019, Travis Everett wrote:
Ryan,
I don't know a ton about how those parts of the codebase work so I st
Ryan,
I don't know a ton about how those parts of the codebase work so I stalled
a bit hoping someone else would respond (there's some chance I'll mis-lead
you here...). In any case, a good place to start is by seeing whether the
behavior changed in 1.8.12/13/14. That should let you narrow your fo
Hello,
Thanks for the reply.
I tried 1.8.11 on my mac and I get a Segmentation fault!
.
.
.
Reading
/Users/relliott/unison-sync/KIM/git/kim-api/fortran/include/kim_model_compute_arguments_module.f90...
Parsing file
/Users/relliott/unison-sync/KIM/git/kim-api/fortran/include/kim_model_compute_
The copy on RTD indicates it was generated by doxygen 1.8.11, while the one
at openkim indicates 1.8.14; a good first step would be installing 1.8.11
and seeing if your output matches what's on RTD.
On Wed, Jan 30, 2019 at 3:08 PM Ryan S. Elliott wrote:
> Hello,
>
> I'm working on the doxygen do
Hello,
I'm working on the doxygen documentation for the kim-api project
(https://github.com/openkim/kim-api)
When I locally (on my mac) generate the doxygen docs I see problems with the
fortran docs. In particular, there are a fair number of functions that are not
automatically documented by th
