src/{builtin,c-types-{impl,parse}}.lisp: Add some more builtin types.
[sod] / src / c-types-parse.lisp
1 ;;; -*-lisp-*-
2 ;;;
3 ;;; Parser for C types
4 ;;;
5 ;;; (c) 2009 Straylight/Edgeware
6 ;;;
7
8 ;;;----- Licensing notice ---------------------------------------------------
9 ;;;
10 ;;; This file is part of the Sensible Object Design, an object system for C.
11 ;;;
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.
16 ;;;
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.
21 ;;;
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.
25
26 (cl:in-package #:sod)
27
28 ;;;--------------------------------------------------------------------------
29 ;;; Declaration specifiers.
30 ;;;
31 ;;; This stuff is distressingly complicated.
32 ;;;
33 ;;; Parsing a (single) declaration specifier is quite easy, and a declaration
34 ;;; is just a sequence of these things. Except that there are a stack of
35 ;;; rules about which ones are allowed to go together, and the language
36 ;;; doesn't require them to appear in any particular order.
37 ;;;
38 ;;; A collection of declaration specifiers is carried about in a purpose-made
39 ;;; object with a number of handy operations defined on it, and then I build
40 ;;; some parsers in terms of them. The basic strategy is to parse
41 ;;; declaration specifiers while they're valid, and keep track of what we've
42 ;;; read. When I've reached the end, we'll convert what we've got into a
43 ;;; `canonical form', and then convert that into a C type object of the
44 ;;; appropriate kind. The whole business is rather more complicated than it
45 ;;; really ought to be.
46
47 ;; Firstly, a table of interesting things about the various declaration
48 ;; specifiers that I might encounter. I categorize declaration specifiers
49 ;; into four kinds.
50 ;;
51 ;; * `Type specifiers' describe the actual type, whether that's integer,
52 ;; character, floating point, or some tagged or user-named type.
53 ;;
54 ;; * `Size specifiers' distinguish different sizes of the same basic type.
55 ;; This is how we tell the difference between `int' and `long'.
56 ;;
57 ;; * `Sign specifiers' distinguish different signednesses. This is how we
58 ;; tell the difference between `int' and `unsigned'.
59 ;;
60 ;; * `Qualifiers' are our old friends `const', `restrict' and `volatile'.
61 ;;
62 ;; These groupings are for my benefit here, in determining whether a
63 ;; particular declaration specifier is valid in the current context. I don't
64 ;; accept `function specifiers' (of which the only current example is
65 ;; `inline') since it's meaningless to me.
66
67 (defclass declspec ()
68 ;; Despite the fact that it looks pretty trivial, this can't be done with
69 ;; `defstruct' for the simple reason that we add more methods to the
70 ;; accessor functions later.
71 ((label :type keyword :initarg :label :reader ds-label)
72 (name :type string :initarg :name :reader ds-name)
73 (kind :type (member type sign size qualifier)
74 :initarg :kind :reader ds-kind)
75 (taggedp :type boolean :initarg :taggedp
76 :initform nil :reader ds-taggedp))
77 (:documentation
78 "Represents the important components of a declaration specifier.
79
80 The only interesting instances of this class are in the table
81 `*declspec-map*'."))
82
83 (defmethod shared-initialize :after ((ds declspec) slot-names &key)
84 "If no name is provided then derive one from the label.
85
86 Most declaration specifiers have simple names for which this works well."
87 (default-slot (ds 'name slot-names)
88 (string-downcase (ds-label ds))))
89
90 (defparameter *declspec-map*
91 (let ((map (make-hash-table :test #'equal)))
92 (dolist (item '((type :void :char :int :float :double
93 (:bool :name "_Bool"))
94 (complexity (:complex :name "_Complex")
95 (:imaginary :name "_Imaginary"))
96 ((type :taggedp t) :enum :struct :union)
97 (size :short :long (:long-long :name "long long"))
98 (sign :signed :unsigned)
99 (qualifier :const :restrict :volatile)))
100 (destructuring-bind (kind &key (taggedp nil))
101 (let ((spec (car item)))
102 (if (consp spec) spec (list spec)))
103 (dolist (spec (cdr item))
104 (destructuring-bind (label
105 &key
106 (name (string-downcase label))
107 (taggedp taggedp))
108 (if (consp spec) spec (list spec))
109 (let ((ds (make-instance 'declspec
110 :label label
111 :name name
112 :kind kind
113 :taggedp taggedp)))
114 (setf (gethash name map) ds
115 (gethash label map) ds))))))
116 (dolist (label '(:complex :imaginary :bool))
117 (setf (gethash (string-downcase label) map) (gethash label map)))
118 map)
119 "Maps symbolic labels and textual names to `declspec' instances.")
120
121 ;; A collection of declaration specifiers, and how to merge them together.
122
123 (defclass declspecs ()
124 ;; This could have been done with `defstruct' just as well, but a
125 ;; `defclass' can be tweaked interactively, which is a win at the moment.
126 ((type :initform nil :initarg :type :reader ds-type)
127 (complexity :initform nil :initarg :complexity :reader ds-complexity)
128 (sign :initform nil :initarg :sign :reader ds-sign)
129 (size :initform nil :initarg :size :reader ds-size)
130 (qualifier :initform nil :initarg :qualifiers :reader ds-qualifiers))
131 (:documentation
132 "Represents a collection of declaration specifiers.
133
134 This is used during type parsing to represent the type under
135 construction. Instances are immutable: we build new ones rather than
136 modifying existing ones. This leads to a certain amount of churn, but
137 we'll just have to live with that.
138
139 (Why are instances immutable? Because it's much easier to merge a new
140 specifier into an existing collection and then check that the resulting
141 thing is valid, rather than having to deal with all of the possible
142 special cases of what the new thing might be. And if the merged
143 collection isn't good, I must roll back to the previous version. So I
144 don't get to take advantage of a mutable structure.)"))
145
146 (defmethod ds-label ((ty c-type)) :c-type)
147 (defmethod ds-name ((ty c-type)) (princ-to-string ty))
148 (defmethod ds-kind ((ty c-type)) 'type)
149
150 (defparameter *good-declspecs*
151 '(((:int) (:signed :unsigned) (:short :long :long-long) ())
152 ((:char) (:signed :unsigned) () ())
153 ((:double) () (:long) (:complex :imaginary))
154 (t () () ()))
155 "List of good collections of declaration specifiers.
156
157 Each item is a list of the form (TYPES SIGNS SIZES COMPLEXITIES). Each of
158 TYPES, SIGNS, SIZES, and COMPLEXITIES, is either a list of acceptable
159 specifiers of the appropriate kind, or T, which matches any specifier.")
160
161 (defun good-declspecs-p (specs)
162 "Are SPECS a good collection of declaration specifiers?"
163 (let ((speclist (list (ds-type specs)
164 (ds-sign specs)
165 (ds-size specs)
166 (ds-complexity specs))))
167 (some (lambda (it)
168 (every (lambda (spec pat)
169 (or (eq pat t) (null spec)
170 (member (ds-label spec) pat)))
171 speclist it))
172 *good-declspecs*)))
173
174 (defun combine-declspec (specs ds)
175 "Combine the declspec DS with the existing SPECS.
176
177 Returns new DECLSPECS if they're OK, or `nil' if not. The old SPECS are
178 not modified."
179
180 (let* ((kind (ds-kind ds))
181 (old (slot-value specs kind)))
182 (multiple-value-bind (ok new)
183 (case kind
184 (qualifier (values t (adjoin ds old)))
185 (size (cond ((not old) (values t ds))
186 ((and (eq (ds-label old) :long) (eq ds old))
187 (values t (gethash :long-long *declspec-map*)))
188 (t (values nil nil))))
189 (t (values (not old) ds)))
190 (if ok
191 (let ((copy (copy-instance specs)))
192 (setf (slot-value copy kind) new)
193 (and (good-declspecs-p copy) copy))
194 nil))))
195
196 (defun declspecs-type (specs)
197 "Convert `declspecs' SPECS into a standalone C type object."
198 (let ((type (ds-type specs))
199 (size (ds-size specs))
200 (sign (ds-sign specs))
201 (quals (mapcar #'ds-label (ds-qualifiers specs))))
202 (cond ((typep type 'c-type)
203 (qualify-c-type type quals))
204 ((or type size sign)
205 (when (and sign (eq (ds-label sign) :signed)
206 (eq (ds-label type) :int))
207 (setf sign nil))
208 (cond ((and (or (null type) (eq (ds-label type) :int))
209 (or size sign))
210 (setf type nil))
211 ((null type)
212 (setf type (gethash :int *declspec-map*))))
213 (make-simple-type (format nil "~{~@[~A~^ ~]~}"
214 (mapcar #'ds-name
215 (remove nil
216 (list sign size type))))
217 quals))
218 (t
219 nil))))
220
221 ;; Parsing declaration specifiers.
222
223 (define-indicator :declspec "<declaration-specifier>")
224
225 (defun scan-declspec
226 (scanner &key (predicate (constantly t)) (indicator :declspec))
227 "Scan a `declspec' from SCANNER.
228
229 If PREDICATE is provided then only succeed if (funcall PREDICATE DECLSPEC)
230 is true, where DECLSPEC is the raw declaration specifier or C-type object,
231 so we won't have fetched the tag for a tagged type yet. If the PREDICATE
232 returns false then the scan fails without consuming input.
233
234 If we couldn't find an acceptable declaration specifier then issue
235 INDICATOR as the failure indicator. Value on success is either a
236 `declspec' object or a `c-type' object."
237
238 ;; Turns out to be easier to do this by hand.
239 (let ((ds (and (eq (token-type scanner) :id)
240 (let ((kw (token-value scanner)))
241 (or (gethash kw *module-type-map*)
242 (gethash kw *declspec-map*))))))
243 (cond ((or (not ds) (and predicate (not (funcall predicate ds))))
244 (values (list indicator) nil nil))
245 ((and (typep ds 'declspec) (ds-taggedp ds))
246 (scanner-step scanner)
247 (if (eq (token-type scanner) :id)
248 (let ((ty (make-c-tagged-type (ds-label ds)
249 (token-value scanner))))
250 (scanner-step scanner)
251 (values ty t t))
252 (values :tag nil t)))
253 (t
254 (scanner-step scanner)
255 (values ds t t)))))
256
257 (defun scan-and-merge-declspec (scanner specs)
258 "Scan a declaration specifier and merge it with SPECS.
259
260 This is a parser function. If it succeeds, it returns the merged
261 `declspecs' object. It can fail either if no valid declaration specifier
262 is found or it cannot merge the declaration specifier with the existing
263 SPECS."
264
265 (with-parser-context (token-scanner-context :scanner scanner)
266 (if-parse (:consumedp consumedp) (scan-declspec scanner)
267 (aif (combine-declspec specs it)
268 (values it t consumedp)
269 (values (list :declspec) nil consumedp)))))
270
271 (export 'parse-c-type)
272 (defun parse-c-type (scanner)
273 "Parse a C type from declaration specifiers.
274
275 This is a parser function. If it succeeds then the result is a `c-type'
276 object representing the type it found. Note that this function won't try
277 to parse a C declarator."
278
279 (with-parser-context (token-scanner-context :scanner scanner)
280 (if-parse (:result specs :consumedp cp)
281 (many (specs (make-instance 'declspecs) it :min 1)
282 (peek (scan-and-merge-declspec scanner specs)))
283 (let ((type (declspecs-type specs)))
284 (if type (values type t cp)
285 (values (list :declspec) nil cp))))))
286
287 ;;;--------------------------------------------------------------------------
288 ;;; Parsing declarators.
289 ;;;
290 ;;; The syntax of declaration specifiers was horrific. Declarators are a
291 ;;; very simple expression syntax, but this time the semantics are awful. In
292 ;;; particular, they're inside-out. If <> denotes mumble of foo, then op <>
293 ;;; is something like mumble of op of foo. Unfortunately, the expression
294 ;;; parser engine wants to apply op of mumble of foo, so I'll have to do some
295 ;;; work to fix the impedance mismatch.
296 ;;;
297 ;;; The currency we'll use is a pair (FUNC . NAME), with the semantics that
298 ;;; (funcall FUNC TYPE) returns the derived type. The result of
299 ;;; `parse-declarator' will be of this form.
300
301 (export 'parse-declarator)
302 (defun parse-declarator (scanner base-type &key kernel abstractp)
303 "Parse a C declarator, returning a pair (C-TYPE . NAME).
304
305 The SCANNER is a token scanner to read from. The BASE-TYPE is the type
306 extracted from the preceding declaration specifiers, as parsed by
307 `parse-c-type'.
308
309 The result contains both the resulting constructed C-TYPE (with any
310 qualifiers etc. as necessary), and the name from the middle of the
311 declarator. The name is parsed using the KERNEL parser provided, and
312 defaults to matching a simple identifier `:id'. This might, e.g., be
313 (? :id) to parse an `abstract declarator' which has optional names.
314
315 There's an annoying ambiguity in the syntax, if an empty KERNEL is
316 permitted. In this case, you must ensure that ABSTRACTP is true so that
317 the appropriate heuristic can be applied. As a convenience, if ABSTRACTP
318 is true then `(? :id)' is used as the default KERNEL."
319 (with-parser-context (token-scanner-context :scanner scanner)
320 (let ((kernel-parser (cond (kernel kernel)
321 (abstractp (parser () (? :id)))
322 (t (parser () :id)))))
323
324 (labels ((qualifiers ()
325 ;; qualifier*
326
327 (parse
328 (seq ((quals (list ()
329 (scan-declspec
330 scanner
331 :indicator :qualifier
332 :predicate (lambda (ds)
333 (and (typep ds 'declspec)
334 (eq (ds-kind ds)
335 'qualifier)))))))
336 (mapcar #'ds-label quals))))
337
338 (star ()
339 ;; Prefix: `*' qualifiers
340
341 (parse (seq (#\* (quals (qualifiers)))
342 (preop "*" (state 9)
343 (cons (lambda (type)
344 (funcall (car state)
345 (make-pointer-type type quals)))
346 (cdr state))))))
347
348 (predict-argument-list-p ()
349 ;; See `prefix-lparen'. Predict an argument list rather
350 ;; than a nested declarator if (a) abstract declarators are
351 ;; permitted and (b) the next token is a declaration
352 ;; specifier or ellipsis.
353 (let ((type (token-type scanner))
354 (value (token-value scanner)))
355 (and abstractp
356 (or (eq type :ellipsis)
357 (and (eq type :id)
358 (or (gethash value *module-type-map*)
359 (gethash value *declspec-map*)))))))
360
361 (prefix-lparen ()
362 ;; Prefix: `('
363 ;;
364 ;; Opening parentheses are treated as prefix operators by
365 ;; the expression parsing engine. There's an annoying
366 ;; ambiguity in the syntax if abstract declarators are
367 ;; permitted: a `(' might be either the start of a nested
368 ;; subdeclarator or the start of a postfix function argument
369 ;; list. The two are disambiguated by stating that if the
370 ;; token following the `(' is a `)' or a declaration
371 ;; specifier, then we have a postfix argument list.
372 (parse
373 (peek (seq (#\(
374 (nil (if (predict-argument-list-p)
375 (values nil nil nil)
376 (values t t nil))))
377 (lparen #\))))))
378
379 (kernel ()
380 (parse (seq ((name (funcall kernel-parser)))
381 (cons #'identity name))))
382
383 (argument-list ()
384 ;; [argument [`,' argument]* [`,' `...']] | `...'
385 ;;
386 ;; The possibility of a trailing `,' `...' means that we
387 ;; can't use the standard `list' parser. Note that, unlike
388 ;; `real' C, we allow an ellipsis even if there are no
389 ;; explicit arguments.
390
391 (let ((args nil))
392 (loop
393 (when (eq (token-type scanner) :ellipsis)
394 (push :ellipsis args)
395 (scanner-step scanner)
396 (return))
397 (multiple-value-bind (arg winp consumedp)
398 (parse (seq ((base-type (parse-c-type scanner))
399 (dtor (parse-declarator scanner
400 base-type
401 :abstractp t)))
402 (make-argument (cdr dtor) (car dtor))))
403 (unless winp
404 (if (or consumedp args)
405 (return-from argument-list (values arg nil t))
406 (return)))
407 (push arg args))
408 (unless (eq (token-type scanner) #\,)
409 (return))
410 (scanner-step scanner))
411 (values (nreverse args) t args)))
412
413 (postfix-lparen ()
414 ;; Postfix: `(' argument-list `)'
415
416 (parse (seq (#\( (args (argument-list)) #\))
417 (postop "()" (state 10)
418 (cons (lambda (type)
419 (funcall (car state)
420 (make-function-type type args)))
421 (cdr state))))))
422
423 (dimension ()
424 ;; `[' c-fragment ']'
425
426 (parse (seq ((frag (parse-delimited-fragment
427 scanner #\[ #\])))
428 (c-fragment-text frag))))
429
430 (lbracket ()
431 ;; Postfix: dimension+
432
433 (parse (seq ((dims (list (:min 1) (dimension))))
434 (postop "[]" (state 10)
435 (cons (lambda (type)
436 (funcall (car state)
437 (make-array-type type dims)))
438 (cdr state)))))))
439
440 ;; And now we actually do the declarator parsing.
441 (parse (seq ((value (expr (:nestedp nestedp)
442
443 ;; An actual operand.
444 (kernel)
445
446 ;; Binary operators. There aren't any.
447 nil
448
449 ;; Prefix operators.
450 (or (star)
451 (prefix-lparen))
452
453 ;; Postfix operators.
454 (or (postfix-lparen)
455 (lbracket)
456 (when nestedp (seq (#\)) (rparen #\))))))))
457 (cons (funcall (car value) base-type) (cdr value))))))))
458
459 ;;;----- That's all, folks --------------------------------------------------