From: Alan Mackenzie <acm@muc.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, monnier@IRO.UMontreal.CA, emacs-devel@gnu.org
Subject: Re: Thoughts on getting correct line numbers in the byte compiler's warning messages
Date: Mon, 12 Nov 2018 14:16:32 +0000 [thread overview]
Message-ID: <20181112141632.GA4459@ACM> (raw)
In-Reply-To: <83k1lja9w6.fsf@gnu.org>
Hello, Eli.
On Sun, Nov 11, 2018 at 17:53:13 +0200, Eli Zaretskii wrote:
> > Date: Sun, 11 Nov 2018 12:59:45 +0000
> > From: Alan Mackenzie <acm@muc.de>
> > Cc: Michael Heerdegen <michael_heerdegen@web.de>, emacs-devel@gnu.org
> >
> > I've now got this working, and created the new, optimistically named,
> > branch /scratch/accurate-warning-pos.
> Thanks.
> +/* Return a new located symbol with the specified SYMBOL and LOCATION. */
> +Lisp_Object
> +build_located_symbol (Lisp_Object symbol, Lisp_Object location)
> +{
> I'd prefer something like symbol_with_pos instead, and accordingly in
> other related symbol names.
DONE.
> +DEFUN ("only-symbol-p", Fonly_symbol_p, Sonly_symbol_p, 1, 1, 0,
> + doc: /* Return t if OBJECT is a symbol, but not a located symbol. */
> + attributes: const)
> + (Lisp_Object object)
> symbol-bare-p?
DONE. (bare-symbol-p)
[ .... ]
> diff --git a/src/lisp.h b/src/lisp.h
> index eb67626..b4fc6f2 100644
> --- a/src/lisp.h
> +++ b/src/lisp.h
> @@ -323,6 +323,64 @@ typedef union Lisp_X *Lisp_Word;
> typedef EMACS_INT Lisp_Word;
> #endif
> +/* A Lisp_Object is a tagged pointer or integer. Ordinarily it is a
> + Lisp_Word. However, if CHECK_LISP_OBJECT_TYPE, it is a wrapper
> + around Lisp_Word, to help catch thinkos like 'Lisp_Object x = 0;'.
> +
> + LISP_INITIALLY (W) initializes a Lisp object with a tagged value
> + that is a Lisp_Word W. It can be used in a static initializer. */
> Looks like you moved a large chunk of lisp.h to a different place in
> the file. Any reasons for that?
I've now moved all but a few inline functions back again.
> +/* FIXME!!! 2018-11-09. Consider using lisp_h_PSEUDOVECTOR here. */
> What is this FIXME about?
It's gone, the issue having been resolved.
> This needs support in src/.gdbinit and documentation.
Not yet done.
> Thanks again for working in this.
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2018-11-12 14:16 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-01 17:59 Thoughts on getting correct line numbers in the byte compiler's warning messages Alan Mackenzie
2018-11-01 22:45 ` Stefan Monnier
2018-11-05 10:53 ` Alan Mackenzie
2018-11-05 15:57 ` Eli Zaretskii
2018-11-05 16:51 ` Alan Mackenzie
2018-11-06 4:34 ` Herring, Davis
2018-11-06 8:53 ` Alan Mackenzie
2018-11-06 13:56 ` Stefan Monnier
2018-11-06 15:11 ` Alan Mackenzie
2018-11-06 16:29 ` Stefan Monnier
2018-11-06 19:15 ` Alan Mackenzie
2018-11-06 20:04 ` Stefan Monnier
2018-11-07 12:35 ` Alan Mackenzie
2018-11-07 17:11 ` Stefan Monnier
2018-11-07 17:00 ` Alan Mackenzie
2018-11-07 17:25 ` Stefan Monnier
2018-11-07 18:47 ` Alan Mackenzie
2018-11-07 19:12 ` Stefan Monnier
2018-11-08 14:08 ` Alan Mackenzie
2018-11-08 17:02 ` Stefan Monnier
2018-11-08 22:13 ` Alan Mackenzie
2018-11-11 12:59 ` Alan Mackenzie
2018-11-11 15:53 ` Eli Zaretskii
2018-11-11 20:12 ` Alan Mackenzie
2018-11-11 20:47 ` Stefan Monnier
2018-11-12 3:30 ` Eli Zaretskii
2018-11-12 16:19 ` Eli Zaretskii
2018-11-12 14:16 ` Alan Mackenzie [this message]
2018-11-12 15:44 ` Alan Mackenzie
2018-11-12 20:36 ` Stefan Monnier
2018-11-12 21:35 ` Alan Mackenzie
2018-11-14 13:34 ` Stefan Monnier
2018-11-15 16:32 ` Alan Mackenzie
2018-11-15 18:01 ` Stefan Monnier
2018-11-16 14:14 ` Alan Mackenzie
2018-11-08 4:47 ` Michael Heerdegen
2018-11-08 11:07 ` Alan Mackenzie
2018-11-09 2:06 ` Michael Heerdegen
2018-11-10 10:59 ` Alan Mackenzie
2018-11-10 13:20 ` Stefan Monnier
2018-11-11 7:56 ` Michael Heerdegen
2018-11-08 13:45 ` Stefan Monnier
2018-11-09 3:06 ` Michael Heerdegen
2018-11-09 16:15 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181112141632.GA4459@ACM \
--to=acm@muc.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=monnier@IRO.UMontreal.CA \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).