summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--doc/ref/ChangeLog5
-rw-r--r--doc/ref/api-utility.texi7
2 files changed, 5 insertions, 7 deletions
diff --git a/doc/ref/ChangeLog b/doc/ref/ChangeLog
index f0b8cde77..58d669c15 100644
--- a/doc/ref/ChangeLog
+++ b/doc/ref/ChangeLog
@@ -1,3 +1,8 @@
+2006-02-13 Marius Vollmer <mvo@zagadka.de>
+
+ * api-utility.texi (Object Properties): Removed confusing
+ paragraph about 'name' property.
+
2006-02-04 Neil Jerram <neil@ossau.uklinux.net>
* api-control.texi (Throw Handlers): New node.
diff --git a/doc/ref/api-utility.texi b/doc/ref/api-utility.texi
index 1305a9259..9f6766c71 100644
--- a/doc/ref/api-utility.texi
+++ b/doc/ref/api-utility.texi
@@ -181,13 +181,6 @@ Scheme object even though that object does not have a dedicated slot
available in which the additional information could be stored. Object
properties allow you to do just that.
-An object property is most commonly used to associate one kind of
-additional information with each instance of a class of similar Scheme
-objects. For example, all procedures have a `name' property, which
-stores the name of the variable in which the procedure was stored by a
-@code{define} expression, or @code{#f} if the procedure wasn't created
-by that kind of expression.
-
Guile's representation of an object property is a procedure-with-setter
(@pxref{Procedures with Setters}) that can be used with the generalized
form of @code{set!} (REFFIXME) to set and retrieve that property for any