After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 602818 - C# files starting with 'namespace' is not parsed
C# files starting with 'namespace' is not parsed
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.1
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 605659 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-11-24 10:34 UTC by Bjørn Ullevoldsæter
Modified: 2009-12-30 13:39 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A C# Console Application and a doxygen config file. (34.59 KB, application/x-zip-compressed)
2009-11-24 10:34 UTC, Bjørn Ullevoldsæter
Details

Description Bjørn Ullevoldsæter 2009-11-24 10:34:03 UTC
Created attachment 148378 [details]
A C# Console Application and a doxygen config file.

Documentation will not be generated for *.cs files with the namespace word in the top of the file, eg:

namespace ConsoleApplication1
{
    .... CODE
}

Adding a dummy comment or just a line break in the top of the file will cause the documentation for the file to be generated, eg:

/***/
namespace ConsoleApplication1
{
    .... CODE
}

NB! This works in version 1.5.5, but NOT in the 1.6.1 version.

To reproduce:

* Unzip the attached console application.
* Run doxygen.config with version 1.6.1
* Open /doc/html/index.html
* Verify that NO documentation is generated.
* Add a line break before namespace in Program.cs
* Run doxygen.config
* Open /doc/html/index.html
* Verify that documentation is generated for the Program class
Comment 1 Dimitri van Heesch 2009-11-28 15:41:24 UTC
The problem is caused by the "byte order mark" in the file
(the file starts with bytes EF BB BF to indicate it is a UTF-8 file, doxygen's did not strip these bytes and as a result the parsing of the first line could be wrong).

I'll fix this in the next release.
Comment 2 Dimitri van Heesch 2009-12-29 19:28:11 UTC
*** Bug 605659 has been marked as a duplicate of this bug. ***
Comment 3 Dimitri van Heesch 2009-12-30 13:39:04 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).