anchor.diff:  ;; TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
   ;; SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
   
  -;; $Id: gerror.lisp,v 1.5 2006-02-26 15:30:01 espen Exp $
  +;; $Id: gerror.lisp,v 1.6 2006-04-25 22:01:12 espen Exp $
   
   
   (in-package "GLIB")
  
positive.code:   ((domain :allocation :alien :type quark :reader gerror-domain)
     (code :allocation :alien :type int :reader gerror-code)
     (message :allocation :alien :type string :reader gerror-message))
    (:metaclass struct-class))
  
  (defbinding (%gerror-copy "g_error_copy") () pointer
    (location pointer))
  
  (defbinding (%gerror-free "g_error_free") () nil
    (location pointer))
  
  (defmethod reference-foreign ((class (eql (find-class 'gerror))) location)
    (declare (ignore class))
    (%gerror-copy location))
  
  (defmethod unreference-foreign ((class (eql (find-class 'gerror))) location)
    (declare (ignore class))
    (%gerror-free location))
  
  
  (define-condition glib-error (error)
    ((code :initarg :domain :reader gerror-code)
  
negative.code:     (funcall (if fatal-p #'error #'warn) condition
       :domain domain :message message)))
  
  #-clisp
  (setf 
   #+cmu(alien:extern-alien "log_handler" alien:system-area-pointer) 
   #+sbcl(sb-alien:extern-alien "log_handler" sb-alien:system-area-pointer)
   (callback-address log-handler))
  
  
  #?(pkg-exists-p "glib-2.0" :atleast-version "2.6.0")
  (progn
    ;; Unfortunately this will only work as long as we don't abort to
    ;; toplevel from within the log handler. If we do that, the next
    ;; invocation of g_log will be handled as a recursion and cause an
    ;; abort (SIGABORT being signaled). To make things even worse, SBCL
    ;; doesn't handle SIGABRT at all.
    (defbinding %log-set-default-handler (nil) pointer
      (log-handler callback)
      (nil null))
    (%log-set-default-handler))
  