From: Jared Stevens Organization: Lineo To: djgpp AT delorie DOT com Subject: Re: Why not DJGPP? Date: Wed, 13 Oct 1999 16:10:39 -0600 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain References: <3804038C DOT DA0D55D2 AT snetch DOT cpg DOT com DOT au> MIME-Version: 1.0 Message-Id: <99101316140000.12068@sparky.lineo.com> Content-Transfer-Encoding: 8bit Reply-To: djgpp AT delorie DOT com On Tue, 12 Oct 1999, you wrote: > > At my school they use Borland C/C++, and my friend and I try to use DJGPP > > whenever we can. The reason my school wont use it is they would have to train > > the teachers with DJGPP, and that would cost more money that it would save. > > The training wouldn't really be that hard would it? The kind of thing the school > would be teaching would be ANSI-C orientated right? Kinda... people in general don't like change a whole lot. If something changes, they have to figure it out... and it will cause them grief and misery. My teachers figure, if it aint broke... don't fix it. > > They've also already bought the Borland C/C++ compiler and it works find for > > them, and they can't find a reason to trash it and throw away their investment. > > Fair enough, Borland isn't that bad a compiler... I'd still work with DJGPP > tho', > but if your school doesn't, why not ask them if you can use DJGPP > instead of BC/++ > to do projects, etc. ? > We do, but sometimes, they want future classes to be able to look at our programs, and use/improve/learn from them. And when we leave, so will DJGPP's presence, and nobody will be able to use our stuff... It's kind of like a legacy thing. -- Jared Stevens