Skip to content
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

Change declaration of Analyzer::configure and Analyzer::end_of_log #36

Open
hamishwillee opened this issue Dec 3, 2015 · 2 comments
Open

Comments

@hamishwillee
Copy link
Contributor

The declaration of these two functions causes Sphinx to chuck out the following error. As a result the functions are documented, but can't be linked to.

default: /vagrant/docs/reference/analyser_reference.rst:7: WARNING: Error when parsing function declaration:
default: If no return type {
default: Invalid definition: Expected identifier in nested name, got keyword: bool [error at 4]
default:   bool Analyzer::configure(INIReader *config UNUSED)
default:   ----^
default: } else if return type {
default: Invalid definition: Expecting "," or ")" in parameters_and_qualifiers, got "U". [error at 43]
default:   bool Analyzer::configure(INIReader *config UNUSED)
default:   -------------------------------------------^
default: }
default: /vagrant/docs/reference/analyser_reference.rst:7: WARNING: Error when parsing function declaration:
default: If no return type {
default: Invalid definition: Expected identifier in nested name, got keyword: void [error at 4]
default:   void Analyzer::end_of_log(uint32_t packet_count UNUSED)
default:   ----^
default: } else if return type {
default: Invalid definition: Expecting "," or ")" in parameters_and_qualifiers, got "U". [error at 48]
default:   void Analyzer::end_of_log(uint32_t packet_count UNUSED)
default:   ------------------------------------------------^
default: }
@peterbarker
Copy link
Contributor

This problem disappeared for me after I did an "rm -rf doxygen/xml doxygen/doxygen_sqlite3.db

I guess "make clean" in docs should work harder? OTOH, those files didn't come back for me...

@peterbarker
Copy link
Contributor

... of course, the docs were not-good and the problem reappeared after re-running doxygen...

@peterbarker peterbarker reopened this Jul 1, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants