GNOME Bugzilla – Bug 724241
Internal inconsistency: namespace in IDL
Last modified: 2014-04-21 10:09:17 UTC
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.
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?
Created attachment 268989 [details] Self contained example to reproduce the issue.
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.
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.
Already integrated in the meantime.
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).