From db02fb2bcb37ab21af78702cddfd425504d13e4d Mon Sep 17 00:00:00 2001 From: Marius Vollmer Date: Mon, 13 Feb 2006 21:43:17 +0000 Subject: [PATCH] (Object Properties): Removed confusing paragraph about 'name' property. --- doc/ref/ChangeLog | 5 +++++ doc/ref/api-utility.texi | 7 ------- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/doc/ref/ChangeLog b/doc/ref/ChangeLog index 325c8842f..ed9b94dc9 100644 --- a/doc/ref/ChangeLog +++ b/doc/ref/ChangeLog @@ -1,3 +1,8 @@ +2006-02-13 Marius Vollmer + + * api-utility.texi (Object Properties): Removed confusing + paragraph about 'name' property. + 2006-02-07 Kevin Ryde * api-modules.texi (Compiled Code Installation): Revise, in particular 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