Date: Mon, 09 Oct 1995 15:29:54 +0100
From: Thomas Eifert <EIFERT AT reze-1 DOT rz DOT rwth-aachen DOT de>
Subject: Re: Many small files versus big clusters
To: DJGPP AT SUN DOT SOE DOT CLARKSON DOT EDU
Reply-To: eifert AT rz DOT rwth-aachen DOT de
Organization: Rechenzentrum RWTH Aachen

>   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
> file in such a way that if the *.O is assembled into a library file each (part
> separated by `#libunit' lines) becomes a separate compilation unit in the
> library file. This would involve minor alterations to the preprocessor and

just enough to make all that stuff incompatible to the rest of the world -
is it that You desire ???

> compiler and assembler and linker, but in my opinion would be worth it. Even
> with 4096-byte clusters a lot of space is wasted at the ends of clusters. When
> someone is looking at his last few meg free hard disk space and is desperately
> wondering what to delete, he very much needs a few big files rather than a lot
> of small files. Please consider this.
> 

Thomas