Re: [Doxygen-users] Variables at absolute location handled incorrectly in Doxygen

[John C. <jca...@no...>]

Scott, 
 
Do you use some sort of preprocessor to convert this "@ 0x1E08"
construct into assembly language, or something? This is not standard C,
at least not any part of the standard of which I am aware. :) 
 
This extension to the language is probably your problem. Is there some
way to put a comment around the construct so Doxygen won't think it's
part of the declaration? Often language pre-processors will allow you to
embed such extensions in standard C comments so the compiler won't
complain. Is this an extension to C that is supported by your
microcontroller C compiler?
 
John
 
-----
John Calcote (jca...@no...)
Sr. Software Engineeer
Novell, Inc.


>>> "Mark E. Scott Jr." <ms...@aw...> 2/7/2006 2:40 pm >>>

Hello,
 
I have noticed that on some of my microcontroller projects, using C,
and having variables with their locations set absolutely, Doxygen shows
the absolute location as the variable name.
 
For instance:
BLOCK_8 stBase @ 0x1E08;
 
This is a variable of type BLOCK_8, at the absolute location 0x1E08. 
However, when it shows up in my output, it reads the variable name as
'x1e08', and links it to a different place than the actual variable
name.
 
Is there anyway to modify my construct such that Doxygen won't believe
that 'x1E08' is the variable name?
 
Many thanks!
 
Mark E. Scott, Jr.
ms...@aw...
AWS, Inc.