change files

[Allan Adler]

As I understand it, one writes a CWEB (or whatever) file for a
particular installation of a program. When one wants to port
the program, one writes a change file that amends the original
CWEB file to reflect the realities of the port. If so, that
suggests that this is a kind of lacuna in the concept of literate
programming: why shouldn't the issues of porting to different
machines also be part of the CWEB document?

Maybe this isn't really an issue. Maybe the endless #ifdef's for
different machines that one sees in some big programs are the answer
and all the writer of CWEB files has to do is articulate the relevant
considerations with each part of the complex code that results.

At any rate, I'd be interested in knowing how people deal with that
kind of code in literate programs.
--
Ignorantly,
Allan Adler <a...@zurich.csail.mit.edu>
* Disclaimer: I am a guest and *not* a member of the MIT CSAIL. My actions and
* comments do not reflect in any way on MIT. Also, I am nowhere near Boston.