Steel Bank Common Lisp

(defstruct (type (:constructor allocate-type (serial-number kind tag
parameters =-name /=-name))
(:predicate type?))
(name nil :type symbol)
(serial-number nil :type integer)
(kind nil :type typekind :read-only t)
(tag nil :read-only t)
(parameters nil :type list :read-only t)
(=-name nil :type symbol)
(/=-name nil :type symbol)
(order-alist nil)
(range-set-encode nil :type symbol)
(range-set-decode nil :type symbol))

When I unlock the package :common-lisp and input them into sbcl:
This is SBCL 0.9.3.36, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
* (sb-ext:unlock-package :common-lisp)

T
* (defstruct (type (:constructor allocate-type (serial-number kind tag
parameters =-name /=-name))
(:predicate type?))
(name nil :type symbol)
(serial-number nil :type integer)
(kind nil :type typekind :read-only t)
(tag nil :read-only t)
(parameters nil :type list :read-only t)
(=-name nil :type symbol)
(/=-name nil :type symbol)
(order-alist nil)
(range-set-encode nil :type symbol)
(range-set-decode nil :type symbol))

debugger invoked on a TYPE-ERROR in thread #<THREAD "initial thread"
{9003311}>:
The value NIL is not of type SB-C::TAIL-SET.

Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.

restarts (invokable by number or by possibly-abbreviated name):
0: [ABORT] Exit debugger, returning to top level.

(SB-C::DEFINITION-TYPE
#<SB-C::CLAMBDA
:%SOURCE-NAME NIL
:%DEBUG-NAME NIL
:KIND :DELETED
:TYPE #<SB-KERNEL:BUILT-IN-CLASSOID FUNCTION (read-only)>
:WHERE-FROM :DEFINED
:VARS NIL {906BB09}>)
0]

-- 
(setq reply-to
  (concatenate 'string "Binghe " "<tianchunbinghe" '(#\@) "gmail.com>"))

On Sun, 24 Jul 2005, Dirk Gerrits wrote:

> * make Lisp put a C++ try/catch block around each call by arcane and
>  non-portable stack manipulations and whatnot.

I think doing something like

void cplusplus_call(void * code, void * args)
{
   // I've no idea about C++ exception syntax, but you get the idea
   try {
     return code(args);
   except {
     return convert_to_lisp_condition(code, args);
   }
}

might work, but this glosses over huge amounts of hair -- it does avoid 
the arcane manipulations by punting them to the C-compiler, though. ;-)

Cheers,

  -- Nikodemus              Schemer: "Buddha is small, clean, and serious."
                   Lispnik: "Buddha is big, has hairy armpits, and laughs."