Mercurial > hg > xemacs-beta
view man/lispref/index.texi @ 5359:f5a5501814f5
Document the CL set functions and #'eql in the Lispref, not just cl.texi
man/ChangeLog addition:
2011-02-19 Aidan Kehoe <kehoea@parhasard.net>
* lispref/lists.texi (Sets And Lists):
Document #'member*, #'remove*, #'delete* in this file. Document
#'memq, #'member, #'remq, #'remove, #'delq, #'delete in terms of
the former functions.
Document #'subsetp, #'union, #'intersection, #'set-difference,
#'set-exclusive-or and their destructive analogues in this file.
* lispref/lists.texi (Association Lists):
Document #'assoc*, #'rassoc* in this file. Document #'assq,
#'assoc, #'rassq, #'rassoc in terms of the first two functions.
* lispref/objects.texi (Equality Predicates):
Document #'eql here, don't leave it to cl.texi.
src/ChangeLog addition:
2011-02-19 Aidan Kehoe <kehoea@parhasard.net>
* fns.c (Fset_exclusive_or):
This function accepts the :stable keyword too, document this in
its arglist.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sat, 19 Feb 2011 11:03:46 +0000 |
parents | 576fb035e263 |
children |
line wrap: on
line source
@c -*-texinfo-*- @setfilename ../../info/index.info @c Indexing guidelines @c I assume that all indexes will be combined. @c Therefore, if a generated findex and permutations @c cover the ways an index user would look up the entry, @c then no cindex is added. @c Concept index (cindex) entries will also be permuted. Therefore, they @c have no commas and few irrelevant connectives in them. @c I tried to include words in a cindex that give the context of the entry, @c particularly if there is more than one entry for the same concept. @c For example, "nil in keymap" @c Similarly for explicit findex and vindex entries, e.g. "print example". @c Error codes are given cindex entries, e.g. "end-of-file error". @c pindex is used for .el files and Unix programs @node Index, , Standard Hooks, Top @unnumbered Index @ignore All variables, functions, keys, programs, files, and concepts are in this one index. All names and concepts are permuted, so they appear several times, one for each permutation of the parts of the name. For example, @code{function-name} would appear as @b{function-name} and @b{name, function-}. Key entries are not permuted, however. @end ignore @c Print the indices @printindex fn