unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Getting the correct line/column numbers on byte compilation error/warning messages
Date: Mon, 17 Jul 2017 17:53:06 +0000	[thread overview]
Message-ID: <20170717175305.GA3647@acm> (raw)
In-Reply-To: <7e588da4-be1e-ae1e-2023-66a9392031f9@gmail.com>

Hello, Clément.

On Mon, Jul 17, 2017 at 12:27:57 +0200, Clément Pit-Claudel wrote:
> On 2017-07-16 15:44, Alan Mackenzie wrote:
> > What do people think?

> I think fixing that problem would be very, very nice.  As to your
> solution: which primitives did you actually have to redefine? It
> sounds like in most cases the new primitives would be very thin
> wrappers around setf, wouldn't they?

Well, it's still a work in progress, so I don't yet know the full set of
new primitives I'll need.  But so far, I've got
(defun bo-cons (kar kdr dest) ...)
(defun bo-dup-hash (src) ...) ; create a new cons with the same hash
    entry as SRC.
(defun bo-reuse-cons (form kons) ...) ; Put the result of FORM into
    kons.
(bo-mapcar (fn list) ...) ; Result list uses cons structure in LIST.
(bo-list-2 (elt0 elt1 dest0 dest1) ; Use DEST[01] to hold the 2 element
    list.
also bo-list-1, bo-list-3, etc,

...amongst a whole lot of half-baked ideas.  It's slowly beginning to
come together, though.  Funnily enough, I haven't used setf a single
time yet.  I've only a vague idea what it does.  I'll need to look it
up.

> Thanks for working on this,

We'll see what we can manage.

> Clément.

-- 
Alan Mackenzie (Nuremberg, Germany).



  reply	other threads:[~2017-07-17 17:53 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 [this message]
2017-07-17 19:42 ` Stefan Monnier
2017-07-17 19:56   ` Alan Mackenzie
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=20170717175305.GA3647@acm \
    --to=acm@muc.de \
    --cc=cpitclaudel@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).