Hi Derek,

My Visual C++ 6.0 installation has source for the
C Run Time library.  File handles returned by
"open" and "create" are NOT Windows API level
file handles.  They are an index into arrays of
an internal library structure which contains a
field for saving the Windows API level file handle.

The Windows Socket API says socket handles MAY be
used as Windows API level file handles:
http://msdn.microsoft.com/library/en-us/winsock/winsock/socket_handles_2.asp
Not as definite as I would prefer.

To assure POSIX semantics it seems we need to insure
file and socket handles exist in a single number space
so they can be used together in a "select" implementation.

How does abstracting all CVS I/O calls for files, pipes
and sockets sound to you?

Conrad



_______________________________________________
Bug-cvs mailing list
Bug-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-cvs

Reply via email to