[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Thoughts on getting correct line numbers in the byte compiler's warn
From: |
Eli Zaretskii |
Subject: |
Re: Thoughts on getting correct line numbers in the byte compiler's warning messages |
Date: |
Mon, 05 Nov 2018 17:57:35 +0200 |
> Date: Mon, 5 Nov 2018 10:53:02 +0000
> From: Alan Mackenzie <address@hidden>
> Cc: address@hidden
>
> The reader would produce, in place of the Lisp_Objects it currently
> does, an object with Lisp_Type 1 (which is currently unused). The rest
> of the object would be an address pointing at two Lisp_Objects, one
> being the "real" read object, the other being a source position.
Sounds gross to me.
Did you consider using mint_ptr objects instead? That'd be still be
gross, but at least we won't introduce another type of Lisp_Object.
Also, what about keeping the source position in some other way, like a
property of some symbol?
- Thoughts on getting correct line numbers in the byte compiler's warning messages, Alan Mackenzie, 2018/11/01
- Re: Thoughts on getting correct line numbers in the byte compiler's warning messages, Stefan Monnier, 2018/11/06
- Re: Thoughts on getting correct line numbers in the byte compiler's warning messages, Alan Mackenzie, 2018/11/06
- Re: Thoughts on getting correct line numbers in the byte compiler's warning messages, Stefan Monnier, 2018/11/06
- Re: Thoughts on getting correct line numbers in the byte compiler's warning messages, Alan Mackenzie, 2018/11/06
- Re: Thoughts on getting correct line numbers in the byte compiler's warning messages, Stefan Monnier, 2018/11/06
- Re: Thoughts on getting correct line numbers in the byte compiler's warning messages, Alan Mackenzie, 2018/11/07
- Re: Thoughts on getting correct line numbers in the byte compiler's warning messages, Stefan Monnier, 2018/11/07