It’s often useful to associate a piece of additional information with a 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.
Guile’s representation of an object property is a procedure-with-setter
(see Procedures with Setters) that can be used with the generalized
set! to set and retrieve that property for any Scheme object. So, setting a
property looks like this:
(set! (my-property obj1) value-for-obj1) (set! (my-property obj2) value-for-obj2)
And retrieving values of the same property looks like this:
(my-property obj1) ⇒ value-for-obj1 (my-property obj2) ⇒ value-for-obj2
To create an object property in the first place, use the
(define my-property (make-object-property))
Create and return an object property. An object property is a
procedure-with-setter that can be called in two ways.
(property obj) val) sets obj’s property
(property obj) returns the current
setting of obj’s property.
A single object property created by
associate distinct property values with all Scheme values that are
eq? (ruling out numeric values).
Internally, object properties are implemented using a weak key hash table. This means that, as long as a Scheme value with property values is protected from garbage collection, its property values are also protected. When the Scheme value is collected, its entry in the property table is removed and so the (ex-) property values are no longer protected by the table.
Guile also implements a more traditional Lispy interface to properties, in which each object has an list of key-value pairs associated with it. Properties in that list are keyed by symbols. This is a legacy interface; you should use weak hash tables or object properties instead.
Return obj’s property list.
Set obj’s property list to alist.
Return the property of obj with name key.