GNOME Bugzilla – Bug 619728
EXTENSION_MAPPING for C# not working
Last modified: 2011-10-05 12:31:52 UTC
Created attachment 162024 [details] [review] patch to rename c# parser to csharp, so it gets recognized in EXTENSION_MAPPING I'm working on a new VB.NET filter and wanted to generate C# code. Therefor I had to map *.vb files to the C# parser, but it doesn't work. Configuration: EXTENSION_MAPPING = .vb=C# FILE_PATTERNS = *.vb OPTIMIZE_OUTPUT_JAVA = YES EXTRACT_ALL = YES With *.cs files renamed to *.vb Doxygen still uses the default C parser configuration. After a closer look at the code, I've found several problems with this configuration. 1. EXTENSION_MAPPING = .vb=C# can't work, because the "#" is recognized as a comment. I've patched the util.cpp to use "csharp" insted of "c#". 2. there are some lines with a hrdcoded detection of *.cs files. docparser.cpp 4984 filedef.cpp 96 (BTW: line 95 for Java as well, bug 567774) pre.l 134 applying attached patches solves this problem.
Created attachment 162025 [details] [review] fix hardcoded checks for *.cs extension
Thanks for the reminder Vsevolod, I'll include your patches in the next release.
This bug was previously marked ASSIGNED, which means it should be fixed in doxygen version 1.7.0. 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.
Please reopen this bug until you have fixed the documentation. There is not even a slight hint that you have to write "csharp" instead of "C#".
(In reply to comment #4) > Please reopen this bug until you have fixed the documentation. There is not > even a slight hint that you have to write "csharp" instead of "C#". To be more precise, config.html#cfg_extension_mapping gives no hint. The help of the GUI frontend has a different problem: It lists C and C++ twice.