Hi!

It just struck me that libssh2_session_startup() has a prototype that accepts an 'int' for the socket in the second argument.

This is all good for the majority of all systems I know of, except for win64. That system has 64bit sockets but 32bit ints (and longs!)...

I believe this is a reason to finally make the libssh2_socket_t type visible in the public headers and introduce a libssh2_session_startup() replacement that uses such a type.

Or can we do it any other way decently?

--

 / daniel.haxx.se
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel

Reply via email to