should UINT32 be a macro or typedef?

Mon Dec 10 12:20:00 GMT 2001

>>>>> "Adam" == Adam Megacz <gcj@lists.megacz.com> writes:

Adam> Somewhere in the headers pulled in by libjava/boehm.cc, one
Adam> header wants UINT32 to be a #define, and another wants it to be
Adam> a typedef. I haven't figured out exactly where the conflict is,
Adam> but when I find it, which one is "right"?
Adam> Right now I just hacked it by #undef UINT32 in boehm.cc, but I'd
Adam> like to come up with a cleaner solution before I submit my
Adam> patch.
Do either the GC or libjava use this? I don't remember ever seeing
it. If that's the case then it is some kind of clash between system
headers. In that scenario any documented fix is fine.
Tom