From: Andrew S. <ac...@sy...> - 2004-11-01 14:31:30
|
Earnie Boyd wrote: >Posted on DATE by AUTHOR Danny Smith > > >>Hey, if you could figure a way to hide the w32api in its own ugly, big >>footprint namespace..... >> >> >> > >That would be wonders for C++. The main headache are all of the macros >used. The ones that are constants can be changed to a const type but then >there are those that emulate functions. What namespace one be good? One >of w32api sounds good but then that implies 64 bit doesn't fit. So one of >winapi is possibly better? Just thinking outloud, sorry ... > >Earnie > > Perhaps its just my own ignorance showing through, but I was under the impression that (at least with g(cc|++) 3.3.x that any macros/pre-processor definitions appeared in the global namespace, irregardless of the namespace that they were defined in. Is there some way around with 3.4.x? I tried at one point of redoing the entire win32api using constants and function stubs, but kept getting stuck on some issues... just can't quite remember what they were now :-). Andrew. |