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 364536 - patch improving recognition of C++ keywords in colorizer (code.l)
patch improving recognition of C++ keywords in colorizer (code.l)
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.3-SVN
Other Cygwin
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2006-10-23 20:03 UTC by Ben Voigt
Modified: 2007-04-05 20:10 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
doxygen_colorize_c++cli.patch (11.36 KB, patch)
2006-10-23 20:09 UTC, Ben Voigt 		none Details | Review

Description Ben Voigt 2006-10-23 20:03:58 UTC 
This patch extends the pretty-printer to support
template-style casts: static_cast, dynamic_cast, const_cast et al
new C++ standard data types: size_t, wchar_t
Microsoft specific context-sensitive keywords for C++/CLI, the .NET extensions to C++: ref class, value class et al, __super, safe_cast, abstract, sealed, property, event, for each (x in y)


I will post a patch for the documentation components shortly (scanner.l and others).
Comment 1 Ben Voigt 2006-10-23 20:09:11 UTC 
Created attachment 75261 [details] [review]
doxygen_colorize_c++cli.patch

Tested on cygwin with a pretty complex C++/CLI codebase.  I am trying to split up a lot of widespread changes into single target patches; the changes as a whole are tested on a huge project with C#, C, C++, C++/CLI and extra dot files.
Comment 2 Dimitri van Heesch 2006-11-05 13:54:39 UTC 
Thanks Ben, I'll include this patch in the next CVS update.
Comment 3 Dimitri van Heesch 2007-04-05 20:10:08 UTC 
This bug was marked "assigned" by me some time ago, which means it should be
fixed in version 1.5.2 and is hereby marked as such. I would kindly request you
to check if this version indeed fixes the problem and reopen the bug report
should you still see the same problem.