Mercurial > hg > xemacs-beta
annotate man/lispref/index.texi @ 5908:6174848f3e6c
Use parse_integer() in read_atom(); support bases with ratios like integers
src/ChangeLog addition:
2015-05-08 Aidan Kehoe <kehoea@parhasard.net>
* data.c (init_errors_once_early):
Move the Qunsupported_type here from numbers.c, so it's available
when the majority of our types are not supported.
* general-slots.h: Add it here, too.
* number.c: Remove the definition of Qunsupported_type from here.
* lread.c (read_atom):
Check if the first character could reflect a rational, if so, call
parse_integer(), don't check the syntax of the other
characters. This allows us to accept the non-ASCII digit
characters too.
If that worked partially, but not completely, and the next char is
a slash, try to parse as a ratio.
If that fails, try isfloat_string(), but only if the first
character could plausibly be part of a float.
Otherwise, treat as a symbol.
* lread.c (read_rational):
Rename from read_integer. Handle ratios with the same radix
specification as was used for integers.
* lread.c (read1):
Rename read_integer in this function. Support the Common Lisp
#NNNrMMM syntax for parsing a number MMM of arbitrary radix NNN.
man/ChangeLog addition:
2015-05-08 Aidan Kehoe <kehoea@parhasard.net>
* lispref/numbers.texi (Numbers):
Describe the newly-supported arbitrary-base syntax for rationals
(integers and ratios). Describe that ratios can take the same base
specification as integers, something also new.
tests/ChangeLog addition:
2015-05-08 Aidan Kehoe <kehoea@parhasard.net>
* automated/lisp-reader-tests.el:
Check the arbitrary-base integer reader syntax support, just
added. Check the reader base support for ratios, just added.
Check the non-ASCII-digit support in the reader, just added.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sat, 09 May 2015 00:40:57 +0100 |
parents | 576fb035e263 |
children |
rev | line source |
---|---|
398 | 1 @c -*-texinfo-*- |
2 @setfilename ../../info/index.info | |
3 | |
4 @c Indexing guidelines | |
5 | |
6 @c I assume that all indexes will be combined. | |
7 @c Therefore, if a generated findex and permutations | |
8 @c cover the ways an index user would look up the entry, | |
9 @c then no cindex is added. | |
10 @c Concept index (cindex) entries will also be permuted. Therefore, they | |
11 @c have no commas and few irrelevant connectives in them. | |
12 | |
13 @c I tried to include words in a cindex that give the context of the entry, | |
14 @c particularly if there is more than one entry for the same concept. | |
15 @c For example, "nil in keymap" | |
16 @c Similarly for explicit findex and vindex entries, e.g. "print example". | |
17 | |
18 @c Error codes are given cindex entries, e.g. "end-of-file error". | |
19 | |
20 @c pindex is used for .el files and Unix programs | |
21 | |
22 @node Index, , Standard Hooks, Top | |
23 @unnumbered Index | |
24 | |
25 @ignore | |
26 All variables, functions, keys, programs, files, and concepts are | |
444 | 27 in this one index. |
398 | 28 |
29 All names and concepts are permuted, so they appear several times, one | |
30 for each permutation of the parts of the name. For example, | |
31 @code{function-name} would appear as @b{function-name} and @b{name, | |
32 function-}. Key entries are not permuted, however. | |
33 @end ignore | |
34 | |
35 @c Print the indices | |
36 | |
37 @printindex fn |