Here's a proposal in the case we decide to keep add_fd with underlying winsock use: - make unavailable by default on win32 the add_fd/remove_fd - make it available statically only if : USE_FD_WSOCK2 or USE_FD_WSOCK1 is defined at compile time if USE_FD_WSOCK2 is defined we include the winsock2 header, if USE_FD_WSOCK1 is used we used the winsock 1 (presently used) header
Note 1: it would be the responsibility of the 3rd app use and link against the appropriate winsock lib if necessary. Note 2: not using the USE_WSOCK* compile time variables would not prevent the 3rd party user to use winsock API with a clear non ambiguous impl. choice. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
