Re: MOP/Macroexpansion
- From: "Andreas Thiele" <nospam@xxxxxxxxxx>
- Date: Tue, 31 May 2005 02:16:56 +0200
Thanks for your answers - both have been important hints for me.
I think Cobis suggestion will lead to some eval or 'compiling by hand', like
Pascal pointed out. I tracked down macroexpansion and have been able to
shift the eval/compile to some other place in my application where it would
occur only seldomly. I wanted to use macroexpansion instead of eval or
compile to get my code compiled in one step.
Fortunately things totally changed and it turned out that I only need to
call my def-class (a modification of defclass) from toplevel.
Although I dynamically generate classes and methods they are only dynamic
during developement. The delivered application will not do any dynamic
defclass or defmethod besides loading my definition file.
So at the moment, my def-class macro works at least in LispWorks like it was
before and I cannot focus on portability yet.
Still a little astonishing for me, that def-class will not be fully expanded
if called at toplevel - and thus is working.
Thanks
Andreas
.
- References:
- MOP/Macroexpansion
- From: Andreas Thiele
- MOP/Macroexpansion
- Prev by Date: Re: Portable AllegroServe + Clisp
- Next by Date: Re: ANN: First meeting of Danish CL User Group
- Previous by thread: Re: MOP/Macroexpansion
- Next by thread: capi/cocoa capturing
- Index(es):