annotate modules/README @ 3017:1e7cc382eb16
[xemacs-hg @ 2005-10-24 10:07:26 by ben]
refactor mc-alloc dependencies
next-error.el, occur.el: Fix some byte-compile warnings.
alloc.c, buffer.c, buffer.h, casetab.c, casetab.h, charset.h, chartab.c, chartab.h, console-impl.h, console-msw-impl.h, console.c, data.c, database.c, device-impl.h, device-msw.c, device.c, dialog-msw.c, elhash.c, events.h, extents-impl.h, extents.c, faces.c, faces.h, file-coding.c, file-coding.h, frame-impl.h, frame.c, glyphs.c, glyphs.h, gui.c, gui.h, keymap.c, lisp.h, lrecord.h, lstream.c, lstream.h, mule-charset.c, objects-impl.h, objects.c, opaque.c, opaque.h, print.c, process.c, procimpl.h, rangetab.c, rangetab.h, scrollbar-gtk.c, scrollbar-msw.c, scrollbar-x.c, scrollbar.c, scrollbar.h, specifier.c, specifier.h, symbols.c, symeval.h, toolbar.c, toolbar.h, tooltalk.c, ui-gtk.c, ui-gtk.h, unicode.c, window-impl.h, window.c:
Eliminate the majority of #ifdef MC_ALLOC occurrences through
macros LCRECORD_HEADER, ALLOC_LCRECORD_TYPE, MALLOCED_STORAGE_SIZE,
etc. (defined in lrecord.h).
| author |
ben |
| date |
Mon, 24 Oct 2005 10:07:42 +0000 |
| parents |
25e260cb7994 |
| children |
da1365dd3f07 |
| rev |
line source |
|
996
|
1 This directory contains a number of XEmacs dynamic modules. These
|
|
|
2 modules can be loaded directly with the command 'M-x load-module'.
|
|
|
3 However, the preferred method of loading a module is to issue a
|
|
|
4 "(require 'module-name)" command to the Lisp interpreter. This will
|
|
|
5 store information so that a later "(unload-feature 'module-name)" can
|
|
|
6 succeed.
|
|
388
|
7
|
|
996
|
8 To compile one of these modules, simply enter the desired directory,
|
|
|
9 type 'configure', and then 'make'. If you are building the module for
|
|
|
10 an installed XEmacs, then 'make install' will place the module in the
|
|
|
11 appropriate directory for XEmacs to find it later (assuming you have
|
|
|
12 permission to write to that directory). A subsequent 'load-module' or
|
|
|
13 'require' will then load the module, as described above.
|
|
388
|
14
|
|
996
|
15 Each of these demonstrates different features and limitations of the
|
|
|
16 XEmacs module loading technology. For a complete discussion on XEmacs
|
|
|
17 dynamic modules, please consult the XEmacs Module Writers Guide, which
|
|
|
18 can be found in the ../info directory.
|
|
388
|
19
|
|
996
|
20 For those wanting to get started with module writing, please see the
|
|
|
21 'sample' directory. It contains two subdirectories: internal and
|
|
|
22 external. The 'internal' subdirectory contains the framework needed to
|
|
|
23 migrate some core piece of XEmacs functionality into code that can
|
|
|
24 either be compiled into the core or built as a separate module. The
|
|
|
25 'external' subdirectory contains the somewhat simpler framework needed
|
|
|
26 to build a module separately from XEmacs. These should be considered
|
|
|
27 starting places for module writing.
|
