[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Merging scratch/no-purespace to remove unexec and purespace
From: |
Stefan Monnier |
Subject: |
Re: Merging scratch/no-purespace to remove unexec and purespace |
Date: |
Fri, 03 Jan 2025 18:50:08 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
> I just reread the code, and #$ may be what we're looking for. It's a
> unique value that we can pass in to Fread (let-binding load-file-name),
> and it already exists. OTOH, it's used for docstrings normally, so it
> may be cleaner to invent new read syntax.
I still don't understand what this is going to be used for, so I'm not
sure how hackish this would be, but indeed #$ can be used to have the
reader return a known, unique object that we can check with `eq`.
Stefan
- Re: Merging scratch/no-purespace to remove unexec and purespace, Stefan Monnier, 2025/01/03
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2025/01/04
- Re: Merging scratch/no-purespace to remove unexec and purespace,
Stefan Monnier <=
- Re: Merging scratch/no-purespace to remove unexec and purespace, Eli Zaretskii, 2025/01/04
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2025/01/04
- Re: Merging scratch/no-purespace to remove unexec and purespace, Eli Zaretskii, 2025/01/04
- Re: Merging scratch/no-purespace to remove unexec and purespace, Andrea Corallo, 2025/01/06
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2025/01/07
- Re: Merging scratch/no-purespace to remove unexec and purespace, Eli Zaretskii, 2025/01/18
- Re: Merging scratch/no-purespace to remove unexec and purespace, Andrea Corallo, 2025/01/18
- Re: Merging scratch/no-purespace to remove unexec and purespace, Pip Cet, 2025/01/19
- Re: Merging scratch/no-purespace to remove unexec and purespace, Andrea Corallo, 2025/01/18
- Re: Merging scratch/no-purespace to remove unexec and purespace, Eli Zaretskii, 2025/01/19