summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLudovic Courtès <ludo@gnu.org>2006-06-16 07:39:59 +0000
committerLudovic Courtès <ludo@gnu.org>2006-06-16 07:39:59 +0000
commit42be21d82afbede08c86bcde8203d1c94fdbd56e (patch)
tree991953d06538fe6d96689f39894a6d4641264fb1
parentad97642e70962bb9ce5a21311f86a1db772189e0 (diff)
downloadguile-42be21d82afbede08c86bcde8203d1c94fdbd56e.tar.gz
Changes from arch/CVS synchronization
-rw-r--r--doc/ref/ChangeLog5
-rw-r--r--doc/ref/api-utility.texi2
2 files changed, 6 insertions, 1 deletions
diff --git a/doc/ref/ChangeLog b/doc/ref/ChangeLog
index 3122bc3d3..d80fba484 100644
--- a/doc/ref/ChangeLog
+++ b/doc/ref/ChangeLog
@@ -1,3 +1,8 @@
+2006-06-16 Ludovic Courtès <ludovic.courtes@laas.fr>
+
+ * api-utility.texi (Equality): Mentioned the behavior of `equal?'
+ for structures (as suggested by Kevin Ryde).
+
2006-06-13 Ludovic Courtès <ludovic.courtes@laas.fr>
* api-compound.texi (Structure Concepts): Mentioned the behavior
diff --git a/doc/ref/api-utility.texi b/doc/ref/api-utility.texi
index 9f6766c71..4a902123e 100644
--- a/doc/ref/api-utility.texi
+++ b/doc/ref/api-utility.texi
@@ -137,7 +137,7 @@ inexact number (even if their value is the same).
Return @code{#t} if @var{x} and @var{y} are the same type, and their
contents or value are equal.
-For a pair, string, vector or array, @code{equal?} compares the
+For a pair, string, vector, array or structure, @code{equal?} compares the
contents, and does so using using the same @code{equal?} recursively,
so a deep structure can be traversed.