> A build system overhaul would also be nice. As it is now, nearly a hundred C
> files are compiled, each containing a single translated string.
So what? It's done automatically, and a complete rebuild (which is needed only
once due to MAKE) takes
(in a Windows XP DOS box with decent *write* caching) maybe 20 seconds. I never
measured this.
If building on a PC XT, bring some patience ;)
> Considering the amount of languages and memory strategies supported,
'memory strategies'?
> it takes AGES to compile them for every configuration.
whatever AGES means; build on a decent system and it's not worth the trouble,
even for 10 languages.
> Does anyone know why the strings were put into separate files in the first
> place?
I wondered myself, 22 years ago.
I don't *know*, but my guess is that the intention was to keep command.com
modular.
So only if a certain feature is included, the corresponding strings would be
included.
In these dark ages, strings would remain resident in memory while executing
external commands. Not good.
today, a modern compiler/linker would detect that certain strings aren't
referenced and would not link
them anyway. but TC/TLINK certainly didn't do this.
Tom
_______________________________________________
Freedos-devel mailing list
Freedos-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-devel
