Date: Tue, 10 Oct 1995 11:15:24 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: "A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk>
Cc: DJGPP AT SUN DOT SOE DOT CLARKSON DOT EDU
Subject: Re: Many small files versus big clusters


On Mon, 9 Oct 1995, 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', then the
> preprocessor could tell the compiler to tell the assembler to set up the *.O

Another solution (which avoids reinventing the wheel) is to hold the 
library sources on a (compressed) archive and add rules to the makefile 
which extract the file before submitting it to the compiler.  Many 
editors and file-management tools have commands which will let you look 
and edit files in an archive as if they were on your disk.  E.g., Emacs 
has and excellent arc-mode library, Norton Commander can display archives 
as directories, etc.

I wouldn't recommend using disk compressors, it's too much hassle, 
especially when something goes wrong with the disk.