What do people think? I'd be willing to take the diff and apply
it to 4.0 if the community thinks its worthwhile/safe.
- Dossy
On 2001.04.13, Mr. Source Forge <[EMAIL PROTECTED]> wrote:
> Support Requests item #416028, was updated on 2001-04-13 14:49
> You can respond by visiting:
> http://sourceforge.net/tracker/?func=detail&atid=203152&aid=416028&group_id=3152
>
> Category: None
> Group: None
> Status: Open
> Priority: 5
> Submitted By: Adam Zell (zellster)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: WInsock2
>
> Initial Comment:
> Moving Windows-specific networking code to use Windows
> Sockets 2.0 is a good thing, as it allows things like
> scatter/gather IO with WSASend, WSARecv, etc.
>
> I have made the changes necessary, and it seems to
> work. The bulk of the changes are changing includes
> from <winsock.h> to <winsock2.h>, and changing
> references to wsock32.{dll,lib} to ws2_32.{dll, lib}.
>
> Files I modified are:
>
> ./include/nsthread.h
> ./tcl8.3.2/win/tclWinNotify.c
> ./tcl8.3.2/win/tclWinPort.h
> ./tcl8.3.2/win/tclWinSock.c
> ./win32/nscgi/nscgi.dsp
> ./win32/nscp/nscp.dsp
> ./win32/nsd/nsd.dsp
> ./win32/nskn/nskn.dsp
> ./win32/nslog/nslog.dsp
> ./win32/nsodbc/nsodbc.dsp
> ./win32/nsperm/nsperm.dsp
> ./win32/nssock/nssock.dsp
> ./win32/nsssl/nsssl.dsp
> ./win32/nstcl/nstcl.dsp
>
> If there is sufficient interest, I can submit a diff.
>
> ----------------------------------------------------------------------
>
> You can respond by visiting:
> http://sourceforge.net/tracker/?func=detail&atid=203152&aid=416028&group_id=3152
--
Dossy Shiobara mail: [EMAIL PROTECTED]
Panoptic Computer Network web: http://www.panoptic.com/
