From: "deckerben" Newsgroups: comp.os.msdos.djgpp References: <3E7049D1 DOT 2954AB52 AT rmcs DOT cranfield DOT ac DOT uk> Subject: Re: RSXNTDJ with DJGPP Date: Sat, 15 Mar 2003 15:57:22 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Lines: 36 Message-ID: <3e733e7c$0$21722$9b622d9e@news.freenet.de> NNTP-Posting-Host: 213.6.62.90 X-Trace: 1047740029 news.freenet.de 21722 213.6.62.90:4708 X-Complaints-To: abuse AT freenet DOT de To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Martin Stromberg" wrote in message news:b4piud$pu7$1 AT antares DOT lu DOT erisoft DOT se... > Kathleen (kathleen DOT olaofe AT rmcs DOT cranfield DOT ac DOT uk) wrote: > : I must say that to a busy want-some-software-that-works like me, > : DJGPP is a nightmare - I eventually got the basic C & C++ with > > It's not. Only (perhaps) the RXSNTDJ part. Agreed. DJGPP is a reputable, industrial-strength, POSIX-compatible programming solution for DOS. When used alone. I also tried "RXSNTDJ" (months ago when I was also brand new to DJGPP) and found it a waste of my time. I did get a few simple programs written, but found that they performed very poorly. And nobody cares when I write "RXSNTDJ" on my resume, anyway :-), but Visual Studio... hmmmm now that is much better *use* of my professional *time* (that is, if the program absolutely must be WINDOZE specific (hope not). Sticking to established standards, and not wasting time with toys has proved itself a very good policy for me, anyway. But I would recommend DJGPP as a development platform to anyone. You can do a lot with it. Interestingly, in doing many software ports, I have found that the ability of any package to build problem-free on a well-equipped DJGPP installation really "separates the men from the boys" in the world of portability. Sadly, some Linux developers are just as blind as the 'DOZE ones, thinking that their unneccessarily forked, memory-mapped, pole()-dependent packages are "portable" just because they can build on both, SUSE and DEBIAN and even RED HAT :-( Ben