From: Eli Zaretskii Newsgroups: comp.os.msdos.djgpp Subject: Re: posix threads with djgpp Date: Sun, 30 Jan 2000 09:53:55 +0200 Organization: NetVision Israel Lines: 18 Message-ID: References: <388DD4EA DOT E8925EBE AT maths DOT unine DOT ch> <86loe8$kbv$1 AT gateway DOT qnx DOT com> NNTP-Posting-Host: is.elta.co.il Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Trace: news.netvision.net.il 949219023 19159 199.203.121.2 (30 Jan 2000 07:57:03 GMT) X-Complaints-To: abuse AT netvision DOT net DOT il NNTP-Posting-Date: 30 Jan 2000 07:57:03 GMT X-Sender: eliz AT is In-Reply-To: To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Errors-To: dj-admin AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Wed, 26 Jan 2000, Damian Yerrick wrote: > >But not everyone is thread saavy, so the FAQ volume quadruple. > >There are people in this newsgroup strugling from DOS --> Un*x. Now > >imagine having to deal with Thread too ... I don't know if the > >advantage will be visible. > > Solution: two libc's. One is a "basic" libc for making "basic" DOS > apps; the other is an "advanced" libc for making threaded apps. The experience of 10 years of DJGPP development suggests that this is a bad idea: it confuses users and causes lots of FAQs. Thus, the current trend in DJGPP is to *eliminate* multiple libraries with similar functionality, as much as possible. Several libraries are already empty (kept only for back-compatibility with old Makefile's): see libpc.a and libg.a in your lib subdirectory.