Mercurial > hg > xemacs-beta
annotate modules/README @ 5294:bbff29a01820
Add compiler macros and compilation sanity-checks for functions with keywords.
2010-10-25 Aidan Kehoe <kehoea@parhasard.net>
Add compiler macros and compilation sanity-checking for various
functions that take keywords.
* byte-optimize.el (side-effect-free-fns): #'symbol-value is
side-effect free and not error free.
* bytecomp.el (byte-compile-normal-call): Check keyword argument
lists for sanity; store information about the positions where
keyword arguments start using the new byte-compile-keyword-start
property.
* cl-macs.el (cl-const-expr-val): Take a new optional argument,
cl-not-constant, defaulting to nil, in this function; return it if
the expression is not constant.
(cl-non-fixnum-number-p): Make this into a separate function, we
want to pass it to #'every.
(eql): Use it.
(define-star-compiler-macros): Use the same code to generate the
member*, assoc* and rassoc* compiler macros; special-case some
code in #'add-to-list in subr.el.
(remove, remq): Add compiler macros for these two functions, in
preparation for #'remove being in C.
(define-foo-if-compiler-macros): Transform (remove-if-not ...) calls to
(remove ... :if-not) at compile time, which will be a real win
once the latter is in C.
(define-substitute-if-compiler-macros)
(define-subst-if-compiler-macros): Similarly for these functions.
(delete-duplicates): Change this compiler macro to use
#'plists-equal; if we don't have information about the type of
SEQUENCE at compile time, don't bother attempting to inline the
call, the function will be in C soon enough.
(equalp): Remove an old commented-out compiler macro for this, if
we want to see it it's in version control.
(subst-char-in-string): Transform this to a call to nsubstitute or
nsubstitute, if that is appropriate.
* cl.el (ldiff): Don't call setf here, this makes for a load-time
dependency problem in cl-macs.el
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Mon, 25 Oct 2010 13:04:04 +0100 |
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. |