Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Bruno Haible <bruno@cl...> - 2004-09-28 19:29:05
In the tests FORMAT.:T.1 FORMAT.:T.2 FORMAT.:T.3 you assume that FORMAT ~10:T
does nothing if the stream is not a pretty-printing stream.
CLISP honors the FORMAT ~10:T even when the stream is a string-stream.
Could you please fix the tests?
From: Bruno Haible <bruno@cl...> - 2004-10-04 14:25:18
Paul F. Dietz wrote:
> > CLISP honors the FORMAT ~10:T even when the stream is a string-stream.
> > Could you please fix the tests?
> Section 22.214.171.124 says:
> ~n,m:T is the same as (pprint-tab :section n m).
> ~n,m:@T is the same as (pprint-tab :section-relative n m).
> The page for PPRINT-TAB says:
> If stream is a pretty printing stream and the value of *print-pretty*
> is true, tabbing is performed; otherwise, pprint-tab has no effect.
Interesting: These two pprint-tab forms don't specify a stream, therefore the
stream on which these forms operate is unspecified:
- The PPRINT-TAB description just says
"stream---an output stream designator"
and the PRIN1 description says
"output-stream---an output stream designator. The default is
- The HyperSpec/Body/glo_s.html#stream_designator description says that
nil denotes "the value of *standard-output* for output stream designators".
Anyway, this is irrelevant here, because CLISP's FORMAT ~T implementation binds
*STANDARD-OUTPUT* to an intermediate pretty-printing stream, while doing
PPRINT-TAB. So it is really capable of honoring FORMAT ~10:T.