>> C was always a compiled language, > > What i mean by text-processing is, that change code.c, depending of what > programmer wants (details and features must be known). For example to > analyze codebase for possible unaligned access and to substitute it with > access methods needed, if another target or more efficient code is going > to be implemented. It's not statically patching code or even ugly > #ifdefs.
I'm not surprised, that "Einstein of our time"[0] had similar ideas about assembler with powerful text-processing macro functionality vs C in the Ph.D work[1]. Wonderful work, but unfortunately useless for current main stream toester (like in `xbill`) hardware... [0] http://www.wired.com/wired/archive/4.12/ffmassalin.html [1] [7.4 Experience, page 117 (pdf.page 133)] and on to bottom. http://citeseer.ist.psu.edu/massalin92synthesi.html ______
