unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Getting the correct line/column numbers on byte compilation error/warning messages
Date: Mon, 17 Jul 2017 19:56:54 +0000	[thread overview]
Message-ID: <20170717195654.GB3647@acm> (raw)
In-Reply-To: <jwvo9six388.fsf-monnier+gmane.emacs.devel@gnu.org>

Hello, Stefan.

On Mon, Jul 17, 2017 at 15:42:00 -0400, Stefan Monnier wrote:

>         Stefan "who'd actually prefer a «real» solution rather than
>                 another hack, but beggars can't be choosers"

I've been thinking about this for nearly a year, and I can't conceive of
a "real" solution which doesn't involve redesigning the byte compiler
from scratch (or even one which does).  Lisp source code doesn't seem to
lend itself to keeping track of source positions as the forms are
manipulated, taken apart, and put together again.

Can you conceive of some better scheme by which accurate line/column
numbers can be output by error messages, and which doesn't involve
rewriting the byte compiler?

What I do anticipate about my hack is, assuming I ever get it working,
it will produce the correct source code positions all the time, not just
most of the time.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2017-07-17 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-16 13:44 Getting the correct line/column numbers on byte compilation error/warning messages Alan Mackenzie
2017-07-17 10:27 ` Clément Pit-Claudel
2017-07-17 17:53   ` Alan Mackenzie
2017-07-17 19:42 ` Stefan Monnier
2017-07-17 19:56   ` Alan Mackenzie [this message]
2017-07-17 20:27     ` 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=20170717195654.GB3647@acm \
    --to=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    --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).