Buy GNU books!
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
For an introduction to metaobjects and the metaobject protocol, see 3.1.1 Metaobjects and the Metaobject Protocol.
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 all determined by the lexical context in which the invocation appears. For example,
(initialize instance initargs)invocation in the default
make-instancemethod is customizable, because the type of the
instanceargument is determined by the class that was passed to
(make <generic> #:name ',name)invocation in
define-genericis 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
4.1 Class Definition 4.2 Instance Creation 4.3 Class Redefinition 4.4 Method Definition 4.5 Generic Function Invocation
|webmaster||delorie software privacy|
|Copyright © 2003 by The Free Software Foundation||Updated Jun 2003|