delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/06/21/17:29:06

From: "A. Sinan Unur" <asu1 AT cornell DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP is in WAY too many pieces
Date: Fri, 20 Jun 1997 17:55:08 -0400
Organization: Cornell University http://www.cornell.edu
Lines: 42
Sender: asu1 AT cornell DOT edu (Verified)
Message-ID: <33AAFC3C.4085@cornell.edu>
References: <19970617192900 DOT PAA16139 AT ladder02 DOT news DOT aol DOT com> <33A6F444 DOT 19EF AT cs DOT com> <5odi90$9mt AT news DOT ox DOT ac DOT uk>
Reply-To: asu1 AT cornell DOT edu
NNTP-Posting-Host: cu-dialup-0017.cit.cornell.edu
Mime-Version: 1.0
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

George Foot wrote:
> 
> the pros are that no one could complain about DJGPP being large any 
> more; 

i say let them complain. i mean, if i create a ten line console program
in vc 4.0, the compiler places a two 1.65 Mb pre-compiled header files
(one for the debug, the other for the release version of the code). i
have a total of 45 Mb under the djgpp tree (adjusted upward for cluster
zie) including several libraries, all the sources, all the documentation
i could get my hands on _and_ my own current projects. i think that is
very reasonable for my favorite compiler.

> than ten megabytes of disk space. As for cons, removing the less-used
> executables is disabling features, and removing documentation is 
> inviting trouble. But at any time if the user finds a desirable 
> feature is missing he/she can download the appropriate zip file and 
> add the extra functionality in much the same way that one can add new 

i think that is wishful thinking given the number of people who do not
even read the readme.1st file. even though it might seem like it can't
hurt to provide an alternative, i am afraid, it will lead to a
significant increase in posts such as "bug in djgpp", "can't compile"
etc etc with a corresponding increase in the number of responses giving
pointers to what they need to download, how to type make etc. i may
sound cynical, but no matter how well what is needed for what is
documented, if people don't read them, i am afraid this is what will
happen.

note that the original poster said "DJGPP is in WAY too many pieces".
not just that it is too big.
-- 
   Sinan
 
*******************************************************************
 A. Sinan Unur                                WWWWWW
                                              |--O+O
 mailto:sinan DOT unur AT cornell DOT edu                C   ^ 
 http://www.people.cornell.edu/pages/asu1/     \  ~/ 

Unsolicited e-mail is _not_ welcome, and will be billed for.
*******************************************************************

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019