Warning: This is the manual of the legacy Guile 2.0 series. You may want to read the manual of the current stable series instead.
Next: Instance Creation Protocol, Previous: Metaclasses, Up: The Metaobject Protocol [Contents][Index]
The aim of the MOP specification in this chapter is to specify all the customizable generic function invocations that can be made by the standard GOOPS syntax, procedures and methods, and to explain the protocol for customizing such invocations.
A generic function invocation is customizable if the types of the
arguments to which it is applied are not completely determined by the
lexical context in which the invocation appears. For example, the
(initialize instance initargs)
invocation in the
default make-instance
method is customizable, because the type of
the instance
argument is determined by the class that was
passed to make-instance
.
(Whereas — to give a counter-example — the (make <generic>
#:name ',name)
invocation in define-generic
is not customizable,
because all of its arguments have lexically determined types.)
When using this rule to decide whether a given generic function invocation is customizable, we ignore arguments that are expected to be handled in method definitions as a single “rest” list argument.
For each customizable generic function invocation, the invocation protocol is explained by specifying