From:	lonniem AT mail DOT utexas DOT edu
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Ideas for DJGPP.
Date:	Sat, 07 Dec 1996 01:37:32 GMT
Organization:	The University of Texas at Austin, Austin, Texas
Lines:	19
Message-ID:	<58aaot$nkn@geraldo.cc.utexas.edu>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 961202080220 DOT 14161C-100000 AT is> <32A30670 DOT 3CA9 AT stud DOT warande DOT ruu DOT nl>
NNTP-Posting-Host:	slip-e-9.ots.utexas.edu
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

I would have to agree.  When I first started using Turbo C++ a couple
of years ago I could barley even get my own programs to compile,
mostly because at that time I had only read a couple of chapters about
C programming and didn't know anything about linking, converting C
source code to machine language or pre-processing or anything.  Now I
think of myself a couple years ago and chuckle.  I didn't even know
what the Include search paths or library serch path's were in TC++.  I
think if DJGPP is used as someone's first compiler, if they can get
past the already steep learning curve of C combined with that of
DJGPP, it is a good thing.  It tells you more about what's going on
when you have to specify a command line or specific search paths and
stuff.  It's a great compiler and I use it the most of any development
system I've got.  Also with MSVC++ and BC++ there is a bit of a
learning curve with all the class browsers and object views and code
straining gadgets that will do your taxes for you as it brews coffee.
I like using MS-DOS edit to edit my programs.  Open two dos windows,
one at the command prompt for compiling and the other in an edit
window.  Just some thoughts.

- Raw text -