Xref: news-dnh.mv.net comp.os.msdos.djgpp:1264 Path: news-dnh.mv.net!mv!news.sprintlink.net!gatech!cs.utk.edu!hydra1a.cs.utk.edu!doolin From: doolin AT hydra1a DOT cs DOT utk DOT edu (David Doolin) Newsgroups: comp.os.msdos.djgpp Subject: Re: How do I get djgpp? Date: 30 Jul 1995 22:47:05 GMT Organization: University of Tennessee Computer Science Lines: 18 Distribution: world References: <3vckm3$ksm AT post DOT tau DOT ac DOT il> <3vdd7qINNrn6 AT CS DOT UTK DOT EDU> <301ae929 DOT sandmann AT praline DOT no DOT NeoSoft DOT com> Reply-To: doolin AT cs DOT utk DOT edu Nntp-Posting-Host: hydra1a.cs.utk.edu To: djgpp AT sun DOT soe DOT clarkson DOT edu Dj-Gateway: from newsgroup comp.os.msdos.djgpp In article <301ae929 DOT sandmann AT praline DOT no DOT NeoSoft DOT com>, Charles Sandmann writes: |> > Don't try and learn C with djgpp! |> |> I used to tell people this too, but now I recommend djgpp for newbies too. |> Why? When programming under DOS, most 16-bit compilers will lock the |> machine and require a reboot with simple programming errors. DJGPP will |> usually catch most of these with a register display, or at least be |> interruptable with CTRL-BREAK. The newbies then moan about registers and |> assembly listings; but once they UNDERSTAND how useful this information is, |> they are much better programmers. I have wasted too much time trying to |> explain memory models, why you can't have an array of 10000 doubles, |> what to do when running the program locks the machine, etc to even consider |> recommending a "traditional" DOS C compiler ever again. I will add only one thing: strap yourself in, 'cause the learning curve is steep! dmd