From:	"bowman" <bowman AT montana DOT com>
Newsgroups:	comp.os.msdos.djgpp
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 990907150816 DOT 27853V-100000 AT is> <01bef9e7$7784b520$9b77dd86 AT PC0776 DOT voeding DOT tno DOT nl>
Subject:	Re: DJGPP/RSXNTDJ vs Mingw32
Lines:	21
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.00.2014.211
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2014.211
Message-ID:	<7_tB3.1426$vW1.7257@newsfeed.slurp.net>
Date:	Wed, 8 Sep 1999 08:01:52 -0600
NNTP-Posting-Host:	208.4.224.63
X-Trace:	newsfeed.slurp.net 936799235 208.4.224.63 (Wed, 08 Sep 1999 09:00:35 CDT)
NNTP-Posting-Date:	Wed, 08 Sep 1999 09:00:35 CDT
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

P.B. Davis <davis AT voeding DOT tno DOT nl> wrote in message
news:01bef9e7$7784b520$9b77dd86 AT PC0776 DOT voeding DOT tno DOT nl...
> I think you are looking at this too GNU-centrically. Are there really
> pressing reasons for an inhabitant of the Windows universe making
> non-bleeding edge applications to learn to use Unix-type tools to do
> unmissable things one can't do with Windows tools.

A good editor (read Vim or emacs) improves productivity, as does 'make'.
For maintenance on larger projects, a decent shell scripting language helps,
but Perl or Python can fill that niche without getting too GNU-centric. All
of these tools are available for the Windows platform.

As far as debugging, Kernighan & Pike, in  _The Practice of Programming_ ,
mention the use the debugger to get the backtrace,  and look at a few
variables when a program dumps core. Otherwise, they find printf  and other
debug statement compiled in generates a lot more meaningful information.

- Raw text -