Mercurial > hg > xemacs-beta
annotate man/lispref/back.texi @ 5089:99f8ebc082d9
Make #'substring an alias of #'subseq; give the latter the byte code.
src/ChangeLog addition:
2010-03-03 Aidan Kehoe <kehoea@parhasard.net>
* fns.c (Fsubstring): Removed.
* search.c (Freplace_match):
* minibuf.c (Ftry_completion):
* lisp.h:
* keymap.c (ensure_meta_prefix_char_keymapp):
* dired.c (user_name_completion, file_name_completion):
* console-x.c (x_canonicalize_console_connection):
* bytecode.c (Bsubseq):
* bytecode-ops.h (subseq):
Move #'substring to Lisp, as an alias for #'subseq; change all
C Fsubstring() calls to Fsubseq(), change the Bsubstring bytecode
to Bsubseq.
Motivation; not accepting vectors in #'substring is incompatible
with GNU, and Common Lisp prefers #'subseq, it has no #'substring.
lisp/ChangeLog addition:
2010-03-03 Aidan Kehoe <kehoea@parhasard.net>
Move byte code #o117 to #'subseq, not #'substring.
Make #'substring available as an alias for #'subseq in Lisp.
* bytecomp.el (79, subseq, substring):
* bytecomp.el (byte-compile-subseq): New.
* update-elc.el (update-elc-chop-extension): Use #'subseq, not
#'substring, the latter is not yet available.
* subr.el (substring): New alias, to #'subseq.
man/ChangeLog addition:
2010-03-03 Aidan Kehoe <kehoea@parhasard.net>
* lispref/tips.texi (Comment Tips):
* lispref/text.texi (Text Properties):
* lispref/strings.texi (Creating Strings):
* lispref/processes.texi (Input to Processes):
* lispref/functions.texi (Argument List):
* lispref/extents.texi (Duplicable Extents):
Move examples that used substring to using subseq; in
strings.texi, do not change the examples, but document that in
this XEmacs, it is an alias for subseq, and that there may be some
incompatibilities if you depend on that.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Wed, 03 Mar 2010 18:40:12 +0000 |
| parents | 3ecd8885ac67 |
| children |
| rev | line source |
|---|---|
| 428 | 1 \input /home/gd/gnu/doc/texinfo.tex @c -*-texinfo-*- |
| 2 @c %**start of header | |
| 3 @setfilename ../../info/back-cover | |
| 4 @settitle XEmacs Lisp Reference Manual | |
| 5 @c %**end of header | |
| 6 . | |
| 7 @sp 7 | |
| 8 @center @titlefont {XEmacs Lisp} | |
| 9 @sp 1 | |
| 10 | |
| 11 @quotation | |
| 12 Most of the XEmacs text editor is written in the programming | |
| 13 language called XEmacs Lisp. You can write new code in XEmacs Lisp and | |
| 14 install it as an extension to the editor. However, XEmacs Lisp is more | |
| 15 than a mere ``extension language''; it is a full computer programming | |
| 16 language in its own right. You can use it as you would any other | |
| 17 programming language. | |
| 18 | |
| 19 Because XEmacs Lisp is designed for use in an editor, it has special | |
| 20 features for scanning and parsing text as well as features for handling | |
| 21 files, buffers, displays, subprocesses, and so on. XEmacs Lisp is | |
| 22 closely integrated with the editing facilities; thus, editing commands | |
| 23 are functions that can also conveniently be called from Lisp programs, | |
| 24 and parameters for customization are ordinary Lisp variables. | |
| 25 | |
| 26 This manual describes XEmacs Lisp. Generally speaking, the earlier | |
| 27 chapters describe features of XEmacs Lisp that have counterparts in | |
| 28 many programming languages, and later chapters describe features that | |
| 29 are peculiar to XEmacs Lisp or relate specifically to editing. | |
| 30 @end quotation | |
| 31 | |
| 32 @hfil | |
| 33 @bye |