I'd just like to chime in and say I see this kind of behavior too, and it's
worse in 1.8.3.1 than it was in 1.6.3 (the version I was using prior to
grabbing 1.8.3.1).  I haven't chased it as carefully as Geoff here, but I
can definitely say that I've seen both macros not getting expanded and
apparent strange behavior regarding finding #included headers in my large
project, that I have a hard time reproducing in a small repro scenario.  

Cheers,
~Brian

-----Original Message-----
From: Geoff Worboys [mailto:ge...@telesiscomputing.com.au] 
Sent: Wednesday, June 05, 2013 5:58 AM
To: doxygen-users@lists.sourceforge.net
Subject: [Doxygen-users] Strange problems with EXPAND_AS_DEFINED

Hi all,

Regarding  doxygen v1.8.4 on Windows 7 (64bit)

I'm having some very odd problems with EXPAND_AS_DEFINED

Basically it comes down to not expanding macros that are
defined inside header files in the project.  If I move the
definition inside the source file it works.

BUT it's not that simple. I've tried and tried to reproduce in
a simple project but can't seem to get the problem to show
itself in a simpler configuration.


As an experiment, I put the macro in its own header file and
placed it along side the other headers of the project.

When I include that header file directly in the source then
doxygen will expand the macro.

If I include that header file from one of the other project
headers (which is included in the source) then doxygen will
NOT expand the macro.

And the strangest one of all:  The header file I called
"testtemp.hpp" and it was expanding fine (when directly
included) until I then created a source file called
"testtemp.cpp" - and bang, suddenly doxygen stopped expanding
the macro.

That last one I tried after a look at the doxygen source, and
I think it confirms my suspicion that doxygen is deciding NOT
to expand my macro because it getting mixed up about file
names.


Now I can create a header just for this macro and remind myself
to include it directly in all sources that need it, but the
macro itself properly belongs in an existing header - it just
won't work in doxygen when I put it there.

I'm not really expect any response from the list, just venting
my frustration.  But if anyone does have any suggestions that
would be great.

-- 
Geoff Worboys
Telesis Computing Pty Ltd


----------------------------------------------------------------------------
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users



------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
_______________________________________________
Doxygen-users mailing list
Doxygen-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/doxygen-users

Reply via email to