nanogui@linuxhacker.org

: Just from my experience, I like to wrap all of my
: header files with #ifdef wrappers.  My habit.  I don't
: see anything wrong with leaving them out (as the code
: *did* compile just fine without them! ;-)

I understand.  But I'd rather not accept patches
for items that don't need it at this time, this complicates the
real understanding for things truely needed for the VxWorks
port.

: So my solution was to use the VxWorks definitions first
: (as I don't have *any* influence/control over #ifdef-ing
: them to work with Microwindows).   If I include the
: <vxWorks.h> file first, then make sure to include
: <windows.h> (which includes <windef.h>) before including
: any ANSI header files, things work.  It's a balancing
: act, but I haven't found any easier way around these
: type conflicts (but I am open to suggestions! :-)

So - 
    Do we need to include <vxWorks.h> in windows.h?
If not, do we need any changes in windows.h or not?

Regards,

Greg



: 
: BAT
: -- 
: Brent A. Thompson, Next Level Communications <www.nlc.com>
: 1776 22nd Street #100, West Des Moines, IA 50266-1444
: EMail: <Thompson@nlc.com>, Phone: (515)991-3853
: 
: