[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: `unreadablep'
From: |
Po Lu |
Subject: |
Re: `unreadablep' |
Date: |
Wed, 15 Dec 2021 17:51:16 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.60 (gnu/linux) |
Ihor Radchenko <yantar92@gmail.com> writes:
> I can see a use of adding extra argument to prin1. If the argument is
> set, prin1 errors when attempting to print unreadable object or
> alternatively prints nil (or other symbol) instead of the unreadable
> object.
Why an extra argument, and not a variable, say,
`throw-printing-unreadably'? There are many callers of prin1 that could
benefit from this.
- Re: `unreadablep', (continued)
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Lars Ingebrigtsen, 2021/12/15
- RE: [External] : Re: `unreadablep', Drew Adams, 2021/12/15
Re: `unreadablep', Ihor Radchenko, 2021/12/15
- Re: `unreadablep',
Po Lu <=
- Re: `unreadablep', Ihor Radchenko, 2021/12/15
- Re: `unreadablep', Ihor Radchenko, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Ihor Radchenko, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Ihor Radchenko, 2021/12/15
- Re: `unreadablep', Po Lu, 2021/12/15
- Re: `unreadablep', Ihor Radchenko, 2021/12/15
Re: `unreadablep', Stefan Monnier, 2021/12/15