Re: Problem with SBCL pprint
Douglas Katzman via Sbcl-help <[email protected]> Tue, 31 Mar 2026 12:28:06 -0400
| Newsgroups | gmane.lisp.steel-bank.general |
|---|---|
| Message-ID | <CAOrNaszDKhU7qt4WmOy430+uBBNLm-bw9Aj13Lh-YtqhAUe_8Q@mail.gmail.com> |
--===============8221458822023846556== Content-Type: multipart/alternative; boundary="000000000000687377064e5474a1" --000000000000687377064e5474a1 Content-Type: text/plain; charset="UTF-8" Based on some discussion here, I think we would be receptive to well-reasoned claims that ~D,~O,~B,~X "definitely" meant that a value is output exactly as specified in the writeup for that directive regardless of *print-pretty*, provided the value is an integer. I think the claim would be along the line that use of PRINC was merely a hidden detail of the implementation in some cases, not a mandate to use it, and that CLHS allows either interpretation of whether to respect *print-pretty* except in the case when PRINC _must_ be called due to the fallback to "~A" when the argument is not an integer. Something like that. --000000000000687377064e5474a1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">Based on=C2=A0some discussion here, I thi= nk we would be receptive to well-reasoned claims that ~D,~O,~B,~X "def= initely" meant that a value is output exactly=C2=A0as specified in the= writeup for that directive regardless of *print-pretty*, provided the valu= e is an integer.=C2=A0 =C2=A0I think the claim would be along the line=C2= =A0that use of PRINC was merely a hidden detail of the implementation in so= me cases, not a mandate to use it, and that CLHS allows either interpretati= on of whether to respect *print-pretty* except in the case when PRINC _must= _ be called due to the fallback to "~A" when the argument is not = an integer. Something like that.</div></div> --000000000000687377064e5474a1-- --===============8221458822023846556== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============8221458822023846556== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Sbcl-help mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sbcl-help --===============8221458822023846556==--