#2909 closed bug (invalid)
TRACE is different in Haiku than it was in BeOS
Reported by: | scottmc | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
When porting Allegr to Haiku we ran into issues with Allegro also defining TRACE, but it worked ok on BeOS, so we have just commented it out for now, but suspected Haiku might have a problem here.
Change History (2)
comment:1 by , 16 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
Thanks for looking into this. I'll dig through the Allegro code now that I know what to look for.
Note:
See TracTickets
for help on using tickets.
The TRACE macro is exactly the same thing. Maybe Debug.h is included somewhere where it shouldn't? I just scanned the Haiku headers, and the only odd place where Debug.h is included is ObjectList.h, but it's the same on BeOS.
In any case, you should be able to find out where Debug.h is included in the Allegro code. If you need Debug.h, you can still use:
After including the file to make the macro available again (include order matters then, of course).