It's hard to use a wrapper interface for transcripts, since it's usually an existing port that the user wants to record.
I suppose we could change the repl to start a nested level when turning on the transcript (think the script command in unix). That might work. On Sun, Sep 20, 2009 at 12:44 PM, Taylor R Campbell <campb...@mumble.net> wrote: > Date: Sun, 20 Sep 2009 12:14:51 -0700 > From: Joe Marshall <jmarsh...@alum.mit.edu> > > I think moving the transcript port from the property list to the port > itself would be worthwhile because this call chain happens a lot. It > would make ports a little bit bigger, but I don't think that's enough > to worry about. > > I'm not particularly concerned about the size of ports, although I > wonder whether it would be better to do transcripts at a different > layer if we want to do them at all, as a wrapper around ports. For > that matter, does anyone ever actually use the transcript feature? > _______________________________________________ MIT-Scheme-devel mailing list MIT-Scheme-devel@gnu.org http://lists.gnu.org/mailman/listinfo/mit-scheme-devel
