[cl-pdf-devel] cl-pdf examples not working in cmucl 19a

[Marc Battyani]

David J Cooper Jr wrote:

> I have seen the kind of error Chisheng refers to below in Allegro as
> well, and I believe it is due to the
>
>    with-standard-io-syntax
>
> in pdf.lisp which binds *print-readably* to T.
>
> I have added a
>
>  ....
>   (let (*print-readably*)
>   ....
>
> within the with-standard-io-syntax in order to suppress the
> *print-readably* being T, and I question whether we really need
> *print-readably* set to T by default throughout cl-pdf and
> cl-typesetting (it was added in release 2.1 of cl-pdf with
> explanation:
>
>     Added a few with-standard-io-syntax so that the pdf are generated
>     correctly when people change the printer settings.
>
> I'm not sure what this means with respect to *print-readably* being T
> or NIL however. With *print-readably* T it makes, for example,
> printing debug output difficult since object instances generally
> cannot be printed without doing something extra (a print-object
> method?)

At least one cl-pdf user uses radix 16 by default. So the pdf files were not
very readable by acrobat ;-)
But you are right, *print-readably* should be nil. Anyway, maybe there is
some bug hiding here, especially if you get a similar error with ACL.

Marc