picolisp

commit f338a761c54677262ff3808988bfef82348ebfe2
parent ecec5492c7a2bbc271163b2e53a001df8d9c0607
Author: Commit-Bot <unknown>
Date:   Fri,  3 Dec 2010 10:15:38 +0000

Automatic commit from picoLisp.tgz, From: Fri, 03 Dec 2010 10:15:38 GMT
Diffstat:
M
ReleaseNotes
 | 
5
++++-
M
doc/refI.html
 | 
5
+++--
M
doc/refS.html
 | 
6
++++--

3 files changed, 11 insertions(+), 5 deletions(-)
diff --git a/ReleaseNotes b/ReleaseNotes
@@ -1,4 +1,4 @@
-12nov10abu
+02dec10abu
 (c) Software Lab. Alexander Burger
 
 
@@ -18,3 +18,6 @@ C. The pre-generated "*.s" files for the 64-bit version are no longer part of
    architectures and operating systems are supported. Instead, they may
    initially be generated with Ersatz PicoLisp, or downloaded from
    "http://software-lab.de/x86-64.linux.tgz".
+
+D. The 'easter' function in "lib/cal.l" is no longer restricted to the years
+   1900 through 2099.
diff --git a/doc/refI.html b/doc/refI.html
@@ -355,8 +355,9 @@ href="refT.html#tolr/3">tolr/3</a></code>.
 <code>fun</code> defaults to <code><a
 href="refP.html#println">println</a></code>. <code>any1</code> and
 <code>any2</code> may specify a range of keys. If <code>any2</code> is greater
-than <code>any1</code>, the traversal will be in opposite direction. If
-<code>flg</code> is non-<code>NIL</code>, partial keys are skipped. See also
+than <code>any1</code>, the traversal will be in opposite direction. Note that
+the keys need not to be atomic, depending on the application's index structure.
+If <code>flg</code> is non-<code>NIL</code>, partial keys are skipped. See also
 <code><a href="refT.html#tree">tree</a></code>, <code><a
 href="refS.html#scan">scan</a></code>, <code><a
 href="refI.html#init">init</a></code> and <code><a
diff --git a/doc/refS.html b/doc/refS.html
@@ -130,8 +130,10 @@ pairs. <code>fun</code> should be a function accepting two arguments for key and
 value. It defaults to <code><a href="refP.html#println">println</a></code>.
 <code>any1</code> and <code>any2</code> may specify a range of keys. If
 <code>any2</code> is greater than <code>any1</code>, the traversal will be in
-opposite direction. If <code>flg</code> is non-<code>NIL</code>, partial keys
-are skipped. See also <code><a href="refT.html#tree">tree</a></code>, <code><a
+opposite direction. Note that the keys need not to be atomic, depending on the
+application's index structure. If <code>flg</code> is non-<code>NIL</code>,
+partial keys are skipped. See also <code><a
+href="refT.html#tree">tree</a></code>, <code><a
 href="refI.html#iter">iter</a></code>, <code><a
 href="refI.html#init">init</a></code> and <code><a
 href="refS.html#step">step</a></code>.