annotate modules/README @ 1333:1b0339b048ce
[xemacs-hg @ 2003-03-02 09:38:37 by ben]
To: xemacs-patches@xemacs.org
PROBLEMS: Include nt/PROBLEMS and update. Add note about incremental
linking badness.
cmdloop.el, custom.el, dumped-lisp.el, files.el, keydefs.el, keymap.el, lisp-mode.el, make-docfile.el, replace.el, simple.el, subr.el, view-less.el, wid-edit.el: Lots of syncing with FSF 21.2.
Use if-fboundp in wid-edit.el.
New file newcomment.el from FSF.
internals/internals.texi: Fix typo.
(Build-Time Dependencies): New node.
PROBLEMS: Delete.
config.inc.samp, xemacs.mak: Eliminate HAVE_VC6, use SUPPORT_EDIT_AND_CONTINUE in its place.
No incremental linking unless SUPPORT_EDIT_AND_CONTINUE, since it
can cause nasty crashes in pdump. Put warnings about this in
config.inc.samp. Report the full compile flags used for src
and lib-src in the Installation output.
alloc.c, lisp.h, ralloc.c, regex.c: Use ALLOCA() in regex.c to avoid excessive stack allocation.
Also fix subtle problem with REL_ALLOC() -- any call to malloc()
(direct or indirect) may relocate rel-alloced data, causing
buffer text to shift. After any such call, regex must update
all its pointers to such data. Add a system, when
ERROR_CHECK_MALLOC, whereby regex.c indicates all the places
it is prepared to handle malloc()/realloc()/free(), and any
calls anywhere in XEmacs outside of this will trigger an abort.
alloc.c, dialog-msw.c, eval.c, event-stream.c, general-slots.h, insdel.c, lisp.h, menubar-msw.c, menubar-x.c: Change *run_hook*_trapping_problems to take a warning class, not
a string. Factor out code to issue warnings, add flag to
call_trapping_problems() to postpone warning issue, and make
*run_hook*_trapping_problems issue their own warnings tailored
to the hook, postponed in the case of safe_run_hook_trapping_problems()
so that the appropriate message can be issued about resetting to
nil only when not `quit'. Make record_unwind_protect_restoring_int()
non-static.
dumper.c: Issue notes about incremental linking problems under Windows.
fileio.c: Mule-ize encrypt/decrypt-string code.
text.h: Spacing changes.
| author |
ben |
| date |
Sun, 02 Mar 2003 09:38:54 +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.
|
