From: Phil Perucci
Subject: CLOS or DEFSTRUCT on clisp/gcl?
Date: 
Message-ID: <45gplv$9bc@access5.digex.net>
For lending structure to data, when using clisp or gcl (free Lisp on
Unix), is CLOS well supported, or should I stick with the older
DEFSTRUCT.  I would prefer to use CLOS, but if CLOS on clisp and/or
gcl is too buggy, please let me know.

I'm not looking for fancy features, just the best way to avoid nested
car (first) and cdr (rest) all over the place...

-- 
==============================================================================
 Phil Perucci ......... ········@access.digex.net ........ Systems Integrator 
 "Visit the Hydrologic Information Center at http://www.nohrsc.nws.gov/~hic"
==============================================================================
From: Jeff Dalton
Subject: Re: CLOS or DEFSTRUCT on clisp/gcl?
Date: 
Message-ID: <813462975.1582@iiltd.demon.co.uk>
In article <··········@access5.digex.net>,
Phil Perucci <········@access5.digex.net> wrote:
>For lending structure to data, when using clisp or gcl (free Lisp on
>Unix), is CLOS well supported, or should I stick with the older
>DEFSTRUCT.  I would prefer to use CLOS, but if CLOS on clisp and/or
>gcl is too buggy, please let me know.
>
>I'm not looking for fancy features, just the best way to avoid nested
>car (first) and cdr (rest) all over the place...

I don't know about clisp.  kcl/gcl uses pcl as its clos, and it
can be kind of slow.  In particular, it compiles some things on
the fly, and in kcl/gcl that means running the C compiler.

For many purposes, defstruct is still a good solution.  You should
even be able to write methods that are specialized on structure
classes.

-- jeff