view modules/README @ 4777:c69aeb86b2a3

Serialise non-default hash table rehash thresholds correctly; use this. src/ChangeLog addition: 2009-12-17 Aidan Kehoe <kehoea@parhasard.net> * elhash.c (HASH_TABLE_DEFAULT_REHASH_THRESHOLD): New macro, giving a default value for a hash table's rehash threshold given its size and test function. (print_hash_table): Print the hash table's rehash threshold if it has a non-default value. Ditto for its rehash size. (Fmake_hash_table): Supply the keyword arguments in a format understood by #'function-arglist. lisp/ChangeLog addition: 2009-12-17 Aidan Kehoe <kehoea@parhasard.net> * mule/make-coding-system.el (fixed-width-create-decode-encode-tables): Use a rehash threshold of 0.999 for this hash table, now that hash table rehash thresholds are serialised correctly; these hash tables will never be resized, and it's not even that important that they are *that* fast, for most of the coding systems they're used a minority of the time.
author Aidan Kehoe <kehoea@parhasard.net>
date Thu, 17 Dec 2009 13:50:45 +0000
parents 25e260cb7994
children da1365dd3f07
line wrap: on
line source

This directory contains a number of XEmacs dynamic modules.  These
modules can be loaded directly with the command 'M-x load-module'.
However, the preferred method of loading a module is to issue a
"(require 'module-name)" command to the Lisp interpreter.  This will
store information so that a later "(unload-feature 'module-name)" can
succeed.

To compile one of these modules, simply enter the desired directory,
type 'configure', and then 'make'.  If you are building the module for
an installed XEmacs, then 'make install' will place the module in the
appropriate directory for XEmacs to find it later (assuming you have
permission to write to that directory).  A subsequent 'load-module' or
'require' will then load the module, as described above.

Each of these demonstrates different features and limitations of the
XEmacs module loading technology.  For a complete discussion on XEmacs
dynamic modules, please consult the XEmacs Module Writers Guide, which
can be found in the ../info directory.

For those wanting to get started with module writing, please see the
'sample' directory.  It contains two subdirectories: internal and
external.  The 'internal' subdirectory contains the framework needed to
migrate some core piece of XEmacs functionality into code that can
either be compiled into the core or built as a separate module.  The
'external' subdirectory contains the somewhat simpler framework needed
to build a module separately from XEmacs.  These should be considered
starting places for module writing.