[plt-scheme] macros that need to eval

From: Robert Bruce Findler (robby at cs.uchicago.edu)
Date: Tue Jan 28 14:30:11 EST 2003

I was thinking of the way that define-record attaches information about
the record that the record-switch extracts to do the arity checking.

I'm not sure about the exact details of your class system, but if you
can separate the first-order compile time information from the
first-class runtime information, you could still have classes derived
from unit imports -- but the compile-time information would have to be
the same for any class defined in the unit (that is, if you invoke the
unit multiple times, all those classes that come from the same
definition must have the same compile-time info).


At Tue, 28 Jan 2003 14:17:46 -0500 (EST), Doug Orleans wrote:
> Robert Bruce Findler writes:
>  > I don't think that you need to evaluate arguments for that. Have a look
>  > at the way define-struct's super types work. (This may be described in
>  > more detail in his ICFP paper or at http://www.htus.org/). You can use
>  > macro-generating macros to transmit information at compile time.
>  > Perhaps that is what you want (or would be happy with...)?
> No, I don't think that would work.  In particular, I want to be able
> to pass a class to a unit which defines a subclass of the class.  I
> don't think you can do this with something like struct type
> descriptors, but I'd be happy to see an example.
> By the way, Matthew's ICFP paper
> (http://www.cs.utah.edu/plt/publications/macromod.pdf) doesn't cover
> record inheritance, and I couldn't find anything relevant in HTUS.
> Did I miss something?
> --dougo at ccs.neu.edu

Posted on the users mailing list.