From: khan AT xraylith DOT wisc DOT edu (Mumit Khan) Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP: the future is... ? Date: 8 Apr 1999 05:07:56 GMT Organization: Center for X-ray Lithography, UW-Madison Lines: 19 Message-ID: <7ehdjc$qh6$1@news.doit.wisc.edu> References: <199903260517 DOT AAA32193 AT envy DOT delorie DOT com> <370b5047 DOT 14095306 AT noticias DOT iies DOT es> <199904061935 DOT PAA01552 AT envy DOT delorie DOT com> <370a8bd5 DOT 29350136 AT noticias DOT iies DOT es> NNTP-Posting-Host: modi.xraylith.wisc.edu To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com [ my apologies to djgpp folks for this off-topic post, but I feel the urge to nip some misinfomation in the bud ] In article <370a8bd5 DOT 29350136 AT noticias DOT iies DOT es>, Guillermo Rodriguez Garcia wrote: > >I know, but I was asking Teun Burgers because he stated that mingw32 >(which I already use as well as djgpp) had thread and socket support, >which I'm afraid is not true, unless he was talking about the Win32 >API. Mingw32 supports all of CRTDLL or MSVCRT runtime, and both of which, to the best of my knowledge, support threading quite well. As for sockets, no Berkeley sockets obviously, but it does support the native winsock sockets. Regards, Mumit