;;;; Objective-CL, an Objective-C bridge for Common Lisp.
;;;; Copyright (C) 2007 Matthias Andreas Benkard.
;;;;
;;;; This program is free software: you can redistribute it and/or
;;;; modify it under the terms of the GNU Lesser General Public License
;;;; as published by the Free Software Foundation, either version 3 of
;;;; the License, or (at your option) any later version.
;;;;
;;;; This program is distributed in the hope that it will be useful, but
;;;; WITHOUT ANY WARRANTY; without even the implied warranty of
;;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
;;;; Lesser General Public License for more details.
;;;;
;;;; You should have received a copy of the GNU Lesser General Public
;;;; License along with this program. If not, see
;;;; .
(in-package #:mulk.objective-cl)
;;;; (@* "Convenience types")
(deftype c-pointer ()
'(satisfies pointerp))
(deftype argument-number ()
`(integer 0 ,call-arguments-limit))
;;;; (@* "Foreign data types")
(defctype char-pointer :pointer)
;;;; (@* "Type specifiers")
(deftype objective-c-type-keyword ()
`(member :id :class :selector :string
:char :short :int :long :long-long
:unsigned-char :unsigned-short :unsigned-int
:unsigned-long :unsigned-long-long :pointer
:float :double :void))
;;;; (@* "Objective-C object wrapper classes")
(with-compilation-unit () ; needed for class finalization
(defclass c-pointer-wrapper ()
((pointer :type c-pointer
:reader pointer-to
:initarg :pointer
:initform (cffi:null-pointer)))))
(defmethod make-load-form ((instance c-pointer-wrapper) &optional environment)
(declare (ignore environment))
;; (TYPE-OF INSTANCE) works because MAKE-POINTER-WRAPPER accepts
;; subclasses of ID as well as ID itself.
`(intern-pointer-wrapper ',(type-of instance)
:pointer (make-pointer
,(pointer-address (pointer-to instance)))))
;; The following may be needed by some implementations (namely Allegro
;; CL).
(eval-when (:compile-toplevel :load-toplevel :execute)
(loop for class-name in '(c2mop:funcallable-standard-object
c-pointer-wrapper)
for class = (find-class class-name nil)
when class
unless (c2mop:class-finalized-p class)
do (c2mop:finalize-inheritance class)))
;; FIXME: I'm not confident about this, but it is needed in order to
;; make (DEFCLASS SELECTOR ...) work.
;;
;; On the other hand, CLISP's implementation notes specify this method
;; to return true by default for "some `obvious' cases" [29.12] such as
;; this one. Therefore, we needn't override it. In fact, we can't, at
;; least without disabling #'s package lock.
#-clisp
(defmethod c2mop:validate-superclass ((class c2mop:funcallable-standard-class)
(superclass standard-class))
t)
(defclass selector (c2mop:funcallable-standard-object c-pointer-wrapper)
()
(:metaclass c2mop:funcallable-standard-class)
(:documentation "An Objective-C method selector.
## Description:
Method selectors are Objective-C's equivalent to what Common Lisp calls
**symbols**. Their use, however, is restricted to retrieving methods by
name.
In Common Lisp, you can **funcall** a __selector__ directly (see the
note below for details and why you may want to do this).
__selector__ objects cannot be created by means of __make-instance__.
Use __find-selector__ instead.
## Note:
Instead of using __invoke__, which is neither macro-friendly nor very
useful for method selection at run-time, you may **funcall** selectors
directly. Naturally, __apply__ works as well.
The following calls are all equivalent:
(invoke-by-name instance \"stringWithCString:encoding:\" \"Mulk.\" 4)
(invoke instance :string-with-c-string \"Mulk.\" :encoding 4)
(funcall (selector \"stringWithCString:encoding:\") instance \"Mulk.\" 4)
(apply (selector \"stringWithCString:encoding:\") (list instance \"Mulk.\" 4))
## See also:
__find-selector__"))
(defmethod shared-initialize :after ((selector selector)
slot-names
&rest initargs
&key
&allow-other-keys)
;; CMUCL 19d does not allow the second argument to
;; PCL:SET-FUNCALLABLE-INSTANCE-FUNCTION to be a closure. As we need
;; to close over SELECTOR, simply using a lambda below leads to weird
;; errors on CMUCL and will not work.
;;
;; In particular, one possible symptom is that SELECTOR may not be a
;; selector but something different when INVOKE-BY-NAME is called.
;;
;; Therefore, we handle this in a somewhat different manner for CMUCL.
;; See SELECTOR-FUNCTION below.
(declare (ignore slot-names initargs))
(c2mop:set-funcallable-instance-function
selector
#-cmu #'(lambda (receiver &rest args)
(apply #'invoke-by-name receiver selector args))
#+cmu (selector-function selector)))
#+cmu
(defun selector-function (selector)
;; FIXME? This is okay, as load-forms for selectors are defined
;; below. Unfortunately, having to call the compiler for each newly
;; interned selector makes COLLECT-SELECTORS slow.
(compile nil `(lambda (receiver &rest args)
(apply #'invoke-by-name receiver ,selector args))))
(defmethod initialize-instance :after ((selector selector)
&rest initargs
&key
&allow-other-keys)
(declare (ignore initargs))
;; Register the selector.
(let ((symbol (intern (selector-name selector) '#:objective-c-selectors)))
(setf (fdefinition symbol) selector)
(export symbol '#:objective-c-selectors)))
(defmethod make-load-form ((selector selector) &optional environment)
(declare (ignore environment))
`(intern-pointer-wrapper 'selector
:pointer (make-pointer
,(pointer-address (pointer-to selector)))))
(defclass id (c-pointer-wrapper)
()
(:documentation "The type of all Objective-C objects.
## Description:
The class __id__ is the supertype of all Objective-C instance types. It
comprises all kinds of Objective-C objects that are instances of some
Objective-C class, that is, neither primitive C values nor __selector__,
__class__ or __exception__ objects.
__id__ objects cannot be created by means of __make-instance__. Use
a suitable class method instead as you would in Objective-C.
## Examples:
(invoke (find-objc-class 'ns-object)
'self)
;=> #
(invoke (find-objc-class 'ns-string)
:string-with-c-string \"Mulk.\")
;=> #
(invoke (find-objc-class 'ns-string)
'new)
;=> #
## See also:
__invoke__, __invoke-by-name__, __exception__"))
(defgeneric objective-c-class-registered-p (class)
(:documentation "Determine whether a class has been registered with the Objective-C runtime.
## Arguments and Values:
*class* --- an **object** of **type** __objective-c-class__.
Returns: a **boolean**.
## Description:
_objective-c-class-registered-p_ determines whether **class** has been
registered with the Objective-C runtime. It is the only public API
provided by the class __objective-c-class__.
A class is registered automatically when an instance is first seen by
Objective-CL or when an attempt is made to send a message to it or its
metaclass.
The effect of attempting to add methods to registered classes is
undefined. Portable programs should therefore avoid it, even though it
may work reliably on some systems (where it can be useful for debugging
and development for portable programs as well).
## Examples:
(define-objective-c-class mlk-my-class ()
((foos :initargs :foos)
(foo-count :foreign-type :int))) ;\"fooCount\" on the foreign side
=> #
(objective-c-class-registered-p (find-objc-class 'mlk-my-class))
=> NIL
(invoke (find-objc-class 'mlk-my-class) 'new)
=> #' {81DE1F8}>
(objective-c-class-registered-p (find-objc-class 'mlk-my-class))
=> T"))
(defclass objective-c-class (standard-class c-pointer-wrapper)
((registered-p :type boolean
:accessor foreign-class-registered-p
:documentation
"Whether the class has been registered with the Objective-C runtime."))
(:documentation "The type of all Objective-C classes.
## Description:
__objective-c-class__ is the supertype of all Objective-C metaclasses
and thus the type of any Objective-C class. The only public API that it
provides is the generic function __objective-c-class-registered-p__ that
determines whether the class has already been registered with the
Objective-C runtime.
## Examples:
(invoke (find-objc-class 'ns-mutable-array) 'self)
=> #<+NS-MUTABLE-ARRAY NS:NS-MUTABLE-ARRAY>
## See also:
__id__, __objective-c-class-registered-p__"))
(defmethod objective-c-class-registered-p ((class objective-c-class))
(foreign-class-registered-p class))
(defclass objective-c-meta-class (objective-c-class)
((fake-p :type boolean
:initform nil
:initarg :fake-p
:accessor metaclass-fake-p
:documentation "Whether the class is a fake metaclass.")))
(define-condition exception (error)
((pointer :type c-pointer
:reader pointer-to
:initarg :pointer))
(:report (lambda (condition stream)
(print-object condition stream)))
(:documentation "The condition type for Objective-C exceptions.
## Description:
Whenever an Objective-C call made by means of __invoke__ or
__invoke-by-name__ raises an exception, the exception is propagated to
the Lisp side by being encapsulated in an __exception__ object and
signaled.
Note that it is currently impossible to directly extract the original
Objective-C exception from an __exception__ object, although it might
arguably be desirable to do so. As __exception__ objects behave just
like __id__ objects in almost all circumstances, this is not much of a
problem, though. If you really do need an __id__ instance rather than
an __exception__, you can simply send it the `self' message.
## Examples:
\(With __install-reader-syntax__ enabled.)
(handler-case
[NSArray selph] ; oops, typo
(exception (e)
e))
;=> #
(class-of *)
;=> #
(class-of [** self])
;=> #
## See also:
__id__"))
(defclass foreign-value (c-pointer-wrapper)
((lisp-managed-cell :type (array boolean ())
:accessor foreign-value-lisp-managed-cell-p
:initarg :lisp-managed-cell
:documentation "Whether we need to handle deallocation."))
(:documentation "A wrapper type for complex foreign values.
## Description:
Whenever a value of a `struct` or `union` type is returned by a method
call or given as an argument to a method implemented in Lisp, it is
encapsulated in a __foreign-value__ that by default deallocates the
value upon its finalisation by the garbage collector.
You can extract a system area pointer that points directly to the
wrapped foreign data by calling __foreign-value-pointer__.
You can control finalisation behaviour by using the
__foreign-value-lisp-managed-p__ accessor.
## See also:
__foreign-value-pointer__, __foreign-value-lisp-managed-p__,
__foreign-struct__, __foreign-union__"))
(defclass foreign-struct (foreign-value)
((name :type (or null string)
:accessor foreign-struct-name
:initarg :name))
(:documentation "A wrapper type for foreign struct values.
## Description:
Foreign values of type `struct` are encapsulated in **object**s of
**type** __foreign-struct__ when returned by a method call or otherwise
acquired by Lisp code through the Objective-C bridge.
For details on how to access the wrapped data and control finalisation
behaviour, see the entry about the type __foreign-value__.
## See also:
__foreign-value-pointer__, __foreign-value-lisp-managed-p__,
__foreign-value__, __foreign-union__"))
(defclass foreign-union (foreign-struct) ()
(:documentation "A wrapper type for foreign union values.
## Description:
Foreign values of type `union` are encapsulated in **object**s of
**type** __foreign-union__ when returned by a method call or otherwise
acquired by Lisp code through the Objective-C bridge.
For details on how to access the wrapped data and control finalisation
behaviour, see the entry about the type __foreign-value__.
## See also:
__foreign-value-pointer__, __foreign-value-lisp-managed-p__,
__foreign-value__, __foreign-struct__"))
;; The following are for private use only.
(defclass opaque-struct (foreign-struct) ())
(defclass tagged-struct (foreign-struct)
((typespec :reader foreign-value-typespec
:initarg :typespec)))
(defclass opaque-union (foreign-union opaque-struct) ())
(defclass tagged-union (foreign-union tagged-struct) ())
(defgeneric foreign-value-pointer (foreign-value)
(:documentation "Access the pointer to the foreign data wrapped by a __foreign-value__.
## Arguments and Values:
*foreign-value* --- an **object** of **type** __foreign-value__.
Returns: a pointer.
## Description:
__foreign-value-pointer__ retrieves a system area pointer that points
directly to the foreign data wrapped by *foreign-value*.
Note that, by default, finalisation of a __foreign-value__ will cause
the data pointed to to be deallocated. See
__foreign-value-lisp-managed-p__ for details and how to control this
behaviour if you need to.
## See also:
__foreign-value-lisp-managed-p__, __foreign-value__"))
(defmethod foreign-value-pointer ((foreign-value foreign-value))
(pointer-to foreign-value))
(defgeneric foreign-value-lisp-managed-p (foreign-value)
(:documentation "Determine or change whether a foreign value will be garbage-collected.
_(setf foreign-value-lisp-managed-p)_ *managed-p* *foreign-value*
## Arguments and Values:
*foreign-value* --- an **object**.
*managed-p* --- a **generalized boolean**.
_foreign-value-lisp-managed-p_ returns: a **boolean**.
## Description:
When a value of a `struct` or `union` type is returned by a method call
or given as an argument to a method implemented in Lisp, it is
encapsulated in a __foreign-value__ that by default deallocates the
value upon its finalisation by the garbage collector.
_foreign-value-lisp-managed-p_ determines whether this automatic
deallocation is enabled. Setting _foreign-value-lisp-managed-p_ to
**false** inhibits automatic deallocation of *foreign-value*.
## Rationale:
Having to manually deallocate all structs returned by values or passed
as arguments to methods implemented in Lisp would require knowledge of
whether a pointer or an actual struct was returned or passed,
respectively. It would also prevent the user from simply discarding
struct return values as any Lisp or Objective-C programmer could
normally do without harm.
On the other hand, automatic deallocation means that anytime the user
wanted to save the struct in a foreign slot as a pointer, they would
need to copy the struct first, which may be expensive and is certainly
inconvenient.
Doing the right thing therefore inevitably implies some kind of user
action some of the time. Requiring the user to mark non-GCable objects
seems like an acceptable trade-off.
## See also:
__foreign-value__"))
(defmethod foreign-value-lisp-managed-p ((foreign-value foreign-value))
(with-slots (lisp-managed-cell) foreign-value
(aref lisp-managed-cell)))
(defgeneric (setf foreign-value-lisp-managed-p) (managedp foreign-value))
(defmethod (setf foreign-value-lisp-managed-p)
(managedp (foreign-value foreign-value))
(with-slots (lisp-managed-cell) foreign-value
(setf (aref lisp-managed-cell) (if managedp t nil))))
(defun make-struct-wrapper (pointer typespec managedp)
;; We use a zero-dimensional array that the finaliser can close over
;; so that it (the finaliser) can decide whether to garbage-collect
;; the foreign data.
;;
;; Using the instance slot directly would be both easier and more
;; transparent, of course, but it also wouldn't work, because during
;; finalisation, the instance is not in a usable state anymore.
(let ((managedp-cell (make-array '() :element-type 'boolean
:initial-element managedp)))
(flet ((finaliser ()
(when (aref managedp-cell)
(foreign-free pointer))))
(let ((new-wrapper (make-instance (ecase (typespec-primary-type typespec)
(struct 'tagged-struct)
(union 'tagged-union))
:name (third typespec)
:typespec typespec
:pointer pointer
:lisp-managed-cell managedp-cell)))
(when managedp
(trivial-garbage:finalize new-wrapper #'finaliser))))))
(defgeneric objcl-eql (obj1 obj2))
(with-compilation-unit ()
(defmethod objcl-eql ((obj1 c-pointer-wrapper) (obj2 c-pointer-wrapper))
(pointer-eq (pointer-to obj1) (pointer-to obj2)))
(defmethod objcl-eql (obj1 obj2)
(eql obj1 obj2)))