view admin/notes/cpp @ 69492:6afc0d1f682b

* mh-compat.el (mh-image-load-path-for-library): Fix example by not recommending that one binds image-load-path. Just defvar it to placate compiler and only use it if previously defined. * mh-e.el (image-load-path): Don't bind! * mh-folder.el (mh-folder-mode): Only use image-load-path if previously defined. * mh-letter.el (mh-letter-mode): Ditto. * mh-utils.el (mh-logo-display): Ditto.
author Bill Wohler <wohler@newt.com>
date Wed, 15 Mar 2006 17:03:58 +0000
parents 695cf19ef79e
children 375f2633d815 c3512b2085a0
line wrap: on
line source

ttn 2003-04-09

we use a C preprocesor not only in the normal compilation of .c files
into object files, but also for creating

	src/Makefile
	lib-src/Makefile

(delimited by comment "start of cpp stuff").  some cpp implementations
insert whitespace in between tokens, which explains the "$(dot)$(dot)"
and "UNEXEC_ALIAS" workarounds for unixoid systems and the bundled
tradcpp/ for vms.  [NOTE: tradcpp/ not yet checked in.]

during makefile creation, the preprocessor symbol NOT_C_CODE is defined.
this should not be defined for normal .c file compilation.

there has been discussion on eliminating this use of cpp and relying
solely on autoconf processing.  rms says to leave it be.

;;; arch-tag: d654291e-9fc8-41b7-ab0c-d3cde842a8e0