[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Ugly, unformatted output from macroexpansion
- To: kettler@MIMSY.CS.UMD.EDU
- Subject: Ugly, unformatted output from macroexpansion
- From: Ralf Moeller <firstname.lastname@example.org>
- Date: Tue, 9 Jun 1992 11:45+0200
- Cc: email@example.com
- In-reply-to: <firstname.lastname@example.org>
- Reply-to: email@example.com
> I'm encountering some strange behavior when I use Ctrl-M to expand a
> macro. On my normal installation of MCL (2.0b1p3) I get an expansion
> of the macro in the listener window, formatted nicely. Recently I tried
> using a saved MCL image from another installation, and when I do Ctrl-M
> the macro expansion appears in the listener window as an unformatted block
> of text (i.e. no spaces or lines between forms).
> I've compared the environment and print options setting on both installations
> and they match (i.e., *print-pretty* is t, etc.). Any ideas why the output
> from the macro expansion is formatted in the one case and not in the other?
I encountered the same problem when I used the Defsystem facility
developed by Mark Kantrowitz (see (member ':mk-defsystem *features*)).
The Defsystem facility redefines the function ccl:require. The new
definition (see the funciton new-require) returns nil even if a module
has been provided. However, the pretty-printer uses the result of require to
check out whether the module PPRINT is available. I changed the definition
of new-require to return t when a module has been provided already.
University of Hamburg
2000 Hamburg 50
Phone: ++40 4123 6134
Fax ++40 4123 6530