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

Internal inconsistency: namespace in IDL (Origin: bugzilla #724241) #5425

Closed
doxygen opened this issue Jul 2, 2018 · 0 comments
Closed

Internal inconsistency: namespace in IDL (Origin: bugzilla #724241) #5425

doxygen opened this issue Jul 2, 2018 · 0 comments

Comments

@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.6 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2014-02-12 16:37:21 +0000, Stephan Seifermann wrote:

After parsing an IDL file, which contains a library definition, I receive the following warning in the configured warnings file:

error: Internal inconsistency: namespace in IDL not module or cg

The error message seems to be not shown completely. Anyhow I think the message should not be displayed at all since I can compile the IDL file successfully. Also I tried an IDL file, which should be free of errors (Example2.idl from http://msdn.microsoft.com/en-us/library/windows/desktop/ms690150%28v=vs.85%29.aspx). The same error appears in the log file.

On 2014-02-12 18:48:53 +0000, albert wrote:

With the i.8.6 version I don't get the message as shown (Just created Example2.idl and Example.idl from the mentioned page), I only get messages about undocumented things)
When looking in the source code of the 1.8.6 version the error message is present but has been removed on December 29, 2013 in github.

Can you test with the github version? or otherwise can you please attach a self-contained example (source+config file in a tar or zip) that allows us to reproduce the problem?

On 2014-02-13 07:37:30 +0000, Stephan Seifermann wrote:

Created attachment 268989
Self contained example to reproduce the issue.

On 2014-02-13 07:40:26 +0000, Stephan Seifermann wrote:

I pulled the current version from github and build it. The error message still exists.

You should be able to reproduce the issue with the attached example. I recognized that after commenting out the EXTRACT_ALL option the warning does not appear anymore. But since I need the undocumented items too this does not really help me.

On 2014-02-20 19:50:23 +0000, albert wrote:

I've pushed a solution to github (pull request 122)

Library was missing in the list of namespaces. In scanner.l constants, module and library are handled in the same way. In namespace.{h,cpp} only constants and module were handled, now also library is handled in a similar way.

On 2014-03-16 17:50:08 +0000, Dimitri van Heesch wrote:

Already integrated in the meantime.

On 2014-04-21 10:09:17 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.7. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).

@doxygen doxygen closed this as completed Jul 2, 2018
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

1 participant