www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1995/10/12/08:03:22

Date: Thu, 12 Oct 1995 12:13:26 +0100
From: Andreas Busse <andy AT soft-n-hard DOT de>
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Subject: Re: Many small files versus big clusters

 >   A.Appleyard wrote:
 > > If (say) all the files LIBSRC\C\IO\*.C are chained into one big file
 > > LIBSRC\C\IO.C, and after each function (plus its associated outermost-level
 > > declarations) you insert a new preprocessor command `#libunit' ...
 > 
 >   dgardner AT mcsilo DOT ilo DOT dec DOT com (Damien Gardner) wrote:-
 > > If (say) all the files LIBSRC\C\IO\*.C are chained into one big file and I
 > > edit one statement in that file and then go to rebuild the library, the
 > > entire body of code has to be recompiled and added to the library ...
 > 
 >   With modern superfast PC's, does the time so saved/wasted matter as much as
 > as it did in the old days?
 > 

I believe the whole discussion is a no-go. Nobody will change 
the structure of the library files since it's simply a waste
of time. In days when you can get a 1 gig harddisk for less
than us$250 such a discussion is rather retro-computing, really.
Furthermore, I don't see a reason to unpack the library as long
you're not trying a fix a bug. And, after fixing, you can pack it
together again saving lots of normally unused disk space. Or
write it onto a tape or whatever.

Cheers,
Andy

-----------------------------------------------------------
Andreas Busse                      | andy AT soft-n-hard DOT de
Soft N Hard GbR                    | Phone: +49 2636-970105
Im Hufen Boden 16, D-53498 Waldorf | Fax:   +49 2636-970106
-----------------------------------------------------------

- Raw text -


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