Mail Archives: djgpp/1995/10/12/10:03:37
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 ...
A.Appleyard wrote back:
> With modern superfast PC's, does the time so saved/wasted matter as much as
> as it did in the old days?
If I remember correctly (and apologies if I get this wrong as I haven't got
the E-Mail anymore) you said that your company got in a load of Pentium 90
machines with 1Gb hard-drives. You also stated that you felt you shouldn't
have to go out and buy more hard-drive space just because there are loads
of little files.
This is perfectly understandable and the argument is a valid one. But now
you suggest a solution that will cause others (like me with my 386dx33)
to feel that we have to go out and buy "superfast PC's" to compile the
library sources.
My thoughts: big hard-drives are cheaper than superfast PC's and it
would not be practical to distribute a BIG-FILE version and a
LOTS-OF-SMALL-FILES version of the libraries.
Oh, yeah ... the DOS JOIN command would be just what you're looking for.
I used to use it to join my RAMDRIVE on D: to look like it was C:\TEMP
and if I didn't load the ramdrive, C:\TEMP was still available but was
my harddrive. UNFORTUNATELY I don't think that this program comes
with DOS 6.22 (and I haven't used it since DOS 5.0). If anybody knows
if this program has changed name or if there is an alternative I'd be
interested to hear from you.
What is 0.02 of an ECU called anyway?
Damien Gardner.
- Raw text -