Now we don't have to choose between the C type and the option type.
fun c-type
func c-type
cl:function function class c-type
- int c-type
+ sod-utilities:int c-type opthandler
kind-c-tagged-type generic
llong c-type
long c-type
(eql fn) t
(eql fun) t
(eql func) t
- (eql int) t
(eql long) t
(eql long-double) t
(eql long-double-complex) t
(eql wchar-t) t
(eql []) t
(eql sod-parser:lisp) t
+ (eql sod-utilities:int) t
cl:string t
expand-c-type-spec
(eql cl:char)
(eql double-imaginary)
(eql float-complex)
(eql float-imaginary)
- (eql int)
(eql llong)
(eql long)
(eql long-double)
(eql va-list)
(eql void)
(eql wchar-t)
+ (eql sod-utilities:int)
cl:list
cl:string
sod-parser:file-location
exit function
help-options optmacro
inc opthandler
- int opthandler
+ sod-utilities:int c-type opthandler
invoke-option-handler function
cl:keyword opthandler
cl:list function class parser opthandler
info function
information class
instance-initargs generic
+ int c-type opthandler
invoke-associated-restart function
it
lbuild-add function
(cl:in-package #:sod-utilities)
+;;;--------------------------------------------------------------------------
+;;; Common symbols.
+;;;
+;;; Sometimes, logically independent packages will want to use the same
+;;; symbol, and these uses (by careful design) don't conflict with each
+;;; other. If we export the symbols here, then the necessary sharing will
+;;; happen automatically.
+
+(export 'int) ; used by c-types and optparse
+
;;;--------------------------------------------------------------------------
;;; Macro hacks.