> c:\fltk-1.3.x-r6960\src\Fl_win32.cxx(236) : warning C4005: 
> 'POLLIN' : macro redefinition
>         C:\Program Files\Microsoft 
> SDKs\Windows\v6.0A\\include\winsock2.h(1495) : see previous 
> definition of 'POLLIN'
> c:\fltk-1.3.x-r6960\src\Fl_win32.cxx(237) : warning C4005: 
> 'POLLOUT' : macro redefinition
>         C:\Program Files\Microsoft 
> SDKs\Windows\v6.0A\\include\winsock2.h(1499) : see previous 
> definition of 'POLLOUT'
> c:\fltk-1.3.x-r6960\src\Fl_win32.cxx(238) : warning C4005: 
> 'POLLERR' : macro redefinition
>         C:\Program Files\Microsoft 
> SDKs\Windows\v6.0A\\include\winsock2.h(1502) : see previous 
> definition of 'POLLERR'

Well, it looks like MS finally got around to defining POLLIN, POLLOUT
and POLLERR.

I guess we need to put an

#ifndef POLLIN
#  define POLLIN 1
#endif

And so forth then...


> c:\fltk-1.3.x-r6960\src\Fl_win32.cxx(1477) : error C2248: 
> 'FORCE_POSITION' : cannot access protected enumerator 
> declared in class 'Fl_Widget'
>         ../..\FL/Fl_Widget.H(151) : see declaration of 
> 'FORCE_POSITION'
>         ../..\FL/Fl_Widget.H(91) : see declaration of 'Fl_Widget'

This is an odd one... Right enough, that enum is "protected" in
Fl_Widget, and Fl_Group (and hence FL_Window) only derive from the
public part of Fl_Widget...

But does that mean we can't look at the enum values...?

Why does no other compiler choke on this. Strange...

I suppose we could put an:
#ifdef _WIN32_
public:
#endif

Type of thing around the enum definition...?









SELEX Sensors and Airborne Systems Limited
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 
3EL
A company registered in England & Wales.  Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to