view admin/notes/cpp @ 65067:52de8046c483

(smerge-basic-map): Bind smerge-combine-with-next. (smerge-auto-leave): Make undo re-enable the mode. (debug-ignored-errors): Add the user-error of impossible resolution. (smerge-resolve): Move things around a bit, in preparation for later. (smerge-diff): Don't fail if the buffer has no associated file. (ediff-ancestor-buffer, ediff-quit-hook): Quieten byte-compiler. (smerge-conflict-overlay): New function. (smerge-match-conflict): Don't add text properties here. (smerge-find-conflict): Instead, add an overlay here. Also check for the case where we're inside a conflict already, so as to obviate the need for font-lock-multiline, which is unbearably slow with large conflicts and ciomplex font-lock patterns. (smerge-remove-props): Remove overlay rather than text-properties. (smerge-mode): Don't set font-lock-multiline. Remove overlays when turned off.
author Stefan Monnier <monnier@iro.umontreal.ca>
date Mon, 22 Aug 2005 14:38:51 +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