3 ;;; Class construction protocol
5 ;;; (c) 2009 Straylight/Edgeware
8 ;;;----- Licensing notice ---------------------------------------------------
10 ;;; This file is part of the Sensible Object Design, an object system for C.
12 ;;; SOD is free software; you can redistribute it and/or modify
13 ;;; it under the terms of the GNU General Public License as published by
14 ;;; the Free Software Foundation; either version 2 of the License, or
15 ;;; (at your option) any later version.
17 ;;; SOD is distributed in the hope that it will be useful,
18 ;;; but WITHOUT ANY WARRANTY; without even the implied warranty of
19 ;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
20 ;;; GNU General Public License for more details.
22 ;;; You should have received a copy of the GNU General Public License
23 ;;; along with SOD; if not, write to the Free Software Foundation,
24 ;;; Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
28 ;;;--------------------------------------------------------------------------
31 (export 'guess-metaclass)
32 (defgeneric guess-metaclass (class)
34 "Determine a suitable metaclass for the CLASS.
36 The default behaviour is to choose the most specific metaclass of any of
37 the direct superclasses of CLASS, or to signal an error if that failed."))
39 (export 'make-sod-class)
40 (defun make-sod-class (name superclasses pset &key location)
41 "Construct and return a new SOD class with the given NAME and SUPERCLASSES.
43 This is the main constructor function for classes. The protocol works as
44 follows. The `:lisp-metaclass' property in PSET is checked: if it exists,
45 it must be a symbol naming a (CLOS) class, which is used in place of
46 `sod-class'. All of the arguments are then passed to `make-instance';
47 further behaviour is left to the standard CLOS instance construction
48 protocol; for example, `sod-class' defines an `:after'-method on
51 Minimal sanity checking is done during class construction; most of it is
52 left for `finalize-sod-class' to do (via `check-sod-class')."
54 (with-default-error-location (location)
55 (let* ((pset (property-set pset))
56 (best-class (or (get-property pset :lisp-metaclass :symbol nil)
57 (select-minimal-class-property
58 superclasses #'class-of #'subtypep 'sod-class
60 :present (lambda (class)
64 (class (make-instance best-class
66 :superclasses superclasses
67 :location (file-location location)
71 ;;;--------------------------------------------------------------------------
72 ;;; Slots and slot initializers.
74 (export 'make-sod-slot)
75 (defgeneric make-sod-slot (class name type pset &key location)
77 "Construct, add, and attach a new slot with given NAME and TYPE, to CLASS.
79 This is the main constructor function for slots. This is a generic
80 function primarily so that the CLASS can intervene in the construction
81 process. The default method uses the `:slot-class' property (defaulting
82 to `sod-slot') to choose a (CLOS) class to instantiate. The slot is then
83 constructed by `make-instance' passing the arguments as initargs; further
84 behaviour is left to the standard CLOS instance construction protocol; for
85 example, `sod-slot' defines an `:after'-method on `shared-initialize'."))
87 (export 'make-sod-instance-initializer)
88 (defgeneric make-sod-instance-initializer
89 (class nick name value pset &key location)
91 "Construct and attach an instance slot initializer, to CLASS.
93 This is the main constructor function for instance initializers. This is
94 a generic function primarily so that the CLASS can intervene in the
95 construction process. The default method looks up the slot using
96 `find-instance-slot-by-name', calls `make-sod-initializer-using-slot' to
97 actually make the initializer object, and adds it to the appropriate list
100 (export 'make-sod-class-initializer)
101 (defgeneric make-sod-class-initializer
102 (class nick name value pset &key location)
104 "Construct and attach a class slot initializer, to CLASS.
106 This is the main constructor function for class initializers. This is a
107 generic function primarily so that the CLASS can intervene in the
108 construction process. The default method looks up the slot using
109 `find-class-slot-by-name', calls `make-sod-initializer-using-slot' to
110 actually make the initializer object, and adds it to the appropriate list
113 (export 'make-sod-initializer-using-slot)
114 (defgeneric make-sod-initializer-using-slot
115 (class slot init-class value pset location)
117 "Common construction protocol for slot initializers.
119 This generic function does the common work for constructing instance and
120 class initializers. It can usefully be specialized according to both the
121 class and slot types. The default method uses the `:initializer-class'
122 property (defaulting to INIT-CLASS) to choose a (CLOS) class to
123 instantiate. The slot is then constructed by `make-instance' passing the
124 arguments as initargs; further behaviour is left to the standard CLOS
125 instance construction protocol; for example, `sod-initializer' defines an
126 `:after'-method on `shared-initialize'.
128 Diagnosing unused properties is left for the caller (usually
129 `make-sod-instance-initializer' or `make-sod-class-initializer') to do.
130 The caller is also expected to have set `with-default-error-location' if
133 You are not expected to call this generic function directly; it's more
134 useful as a place to hang methods for custom initializer classes."))
136 (export 'make-sod-user-initarg)
137 (defgeneric make-sod-user-initarg
138 (class name type pset &key default location)
140 "Attach a user-defined initialization keyword argument to the CLASS.
142 The new argument has the given NAME and TYPE, and maybe a DEFAULT value.
143 Currently, initialization arguments are just dumb objects held in a
146 (export 'make-sod-slot-initarg)
147 (defgeneric make-sod-slot-initarg
148 (class name nick slot-name pset &key location)
150 "Attach an initialization keyword argument to a slot by name.
152 The default method uses `find-instance-slot-by-name' to find the slot, and
153 `make-slot-initarg-using-slot' to actually make and attach the initarg."))
155 (export 'make-sod-slot-initarg-using-slot)
156 (defgeneric make-sod-slot-initarg-using-slot
157 (class name slot pset &key location)
159 "Attach an initialization keyword argument to a SLOT.
161 The argument's type is taken from the slot type. Slot initargs can't have
162 defaults: the slot's most-specific initializer is used instead.
164 You are not expected to call this generic function directly; it's more
165 useful as a place to hang methods for custom classes."))
167 (export 'sod-initarg-argument)
168 (defgeneric sod-initarg-argument (initarg)
169 (:documentation "Returns an `argument' object for the initarg."))
171 (export 'make-sod-class-initfrag)
172 (defgeneric make-sod-class-initfrag (class frag pset &key location)
174 "Attach an initialization fragment FRAG to the CLASS.
176 Currently, initialization fragments are just dumb objects held in a
179 (export 'make-sod-class-tearfrag)
180 (defgeneric make-sod-class-tearfrag (class frag pset &key location)
182 "Attach a teardown fragment FRAG to the CLASS.
184 Currently, teardown fragments are just dumb objects held in a
187 ;;;--------------------------------------------------------------------------
188 ;;; Messages and methods.
190 (export 'make-sod-message)
191 (defgeneric make-sod-message (class name type pset &key location)
193 "Construct and attach a new message with given NAME and TYPE, to CLASS.
195 This is the main constructor function for messages. This is a generic
196 function primarily so that the CLASS can intervene in the construction
197 process. The default method uses the `:message-class' property to choose
198 a (CLOS) class to instantiate; if no such property is provided but a
199 `combination' property is present, then `aggregating-message' is chosen;
200 otherwise `standard-message' is used. The message is then constructed by
201 `make-instance' passing the arguments as initargs; further behaviour is
202 left to the standard CLOS instance construction protocol; for example,
203 `sod-message' defines an `:after'-method on `shared-initialize'."))
205 (export 'make-sod-method)
206 (defgeneric make-sod-method
207 (class nick name type body pset &key location)
209 "Construct and attach a new method to CLASS.
211 This is the main constructor function for methods. This is a generic
212 function primarily so that the CLASS can intervene in the message lookup
213 process, though this is actually a fairly unlikely occurrence.
215 The default method looks up the message using `find-message-by-name',
216 invokes `make-sod-method-using-message' to make the method object, and
217 then adds the method to the class's list of methods. This split allows
218 the message class to intervene in the class selection process, for
221 (export 'make-sod-method-using-message)
222 (defgeneric make-sod-method-using-message
223 (message class type body pset location)
225 "Main construction subroutine for method construction.
227 This is a generic function so that it can be specialized according to both
228 a class and -- more particularly -- a message. The default method uses
229 the `:method-class' property (defaulting to the result of calling
230 `sod-message-method-class') to choose a (CLOS) class to instantiate. The
231 method is then constructed by `make-instance' passing the arguments as
232 initargs; further behaviour is left to the standard CLOS instance
233 construction protocol; for example, `sod-method' defines an
234 `:after'-method on `shared-initialize'.
236 Diagnosing unused properties is left for the caller (usually
237 `make-sod-method') to do. The caller is also expected to have set
238 `with-default-error-location' if appropriate.
240 You are not expected to call this generic function directly; it's more
241 useful as a place to hang methods for custom method classes."))
243 (export 'sod-message-method-class)
244 (defgeneric sod-message-method-class (message class pset)
246 "Return the preferred class for methods on MESSAGE.
248 The message can inspect the PSET to decide on a particular message. A
249 `:method-class' property will usually override this decision: it's then
250 the programmer's responsibility to ensure that the selected method class
253 (export 'check-message-type)
254 (defgeneric check-message-type (message type)
256 "Check that TYPE is a suitable type for MESSAGE. Signal errors if not.
258 This is separated out of `shared-initialize', where it's called, so that
259 it can be overridden conveniently by subclasses."))
261 (export 'check-method-type)
262 (defgeneric check-method-type (method message type)
264 "Check that TYPE is a suitable type for METHOD. Signal errors if not.
266 This is separated out of `shared-initialize', where it's called, so that
267 it can be overridden conveniently by subclasses."))
269 ;;;----- That's all, folks --------------------------------------------------