On Dec 28, 2007 11:33 AM, Robert Dodier <robert.dodier at gmail.com> wrote:
> On 12/17/07, Richard Fateman <fateman at cs.berkeley.edu> wrote:
>
> > Please consider the re-definition of nformat, part of the display
> program,...
>
> After looking over this code, I don't think NFORMAT should emit
> strings for non-string arguments such as numbers or CLOS objects.
> I think Stavros said the same thing about an earlier version....
Actually Fateman agreed that nformat shouldn't perform structure-to-string
conversions in his mail of Dec 20, 2007 4:27 PM, so it's this same version.
Expanding NFORMAT to handle CLOS objects makes sense to me,
> although I would rather see a cons returned instead of a string,
> e.g. ((MLIST) FOO BAR) for an interval instead of "[foo, bar]".
>
I'd think you'd want to have part( interval(2,3) , 0 ) => 'interval or some
such, not "[". You'd do this by having nformat generate ((%interval) 2 3),
with simp-%interval transforming this to whatever CLOS object you want.
> I think that's how NFORMAT works on special cases at present.
>
Which cases did you have in mind?
-s