From: Mark H Weaver <mhw@netris.org>
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Prevent 'error' from being tail-called, for better diagnostics
Date: Mon, 30 Jan 2012 11:32:08 -0500 [thread overview]
Message-ID: <8762fti22f.fsf@netris.org> (raw)
In-Reply-To: <87zkd5wive.fsf@pobox.com> (Andy Wingo's message of "Mon, 30 Jan 2012 12:05:25 +0100")
Andy Wingo <wingo@pobox.com> writes:
> On Mon 30 Jan 2012 07:39, Mark H Weaver <mhw@netris.org> writes:
>
>> One idea is to change 'error' into a macro, and use tricks similar to
>> what 'load' does, to cleverly makes it look like a procedure.
>
> Unfortunately this is an incompatible change. Existing compiled files
> which reference the "error" binding expect it to be a procedure, not a
> macro.
Ah, good point. Damn.
> To provide this source information, a technique like this one might be
> applicable:
>
> http://funcall.blogspot.com/2009/05/you-knew-id-say-something-part-iv.html
Thanks for the pointer, that sounds like a great strategy!
Mark
prev parent reply other threads:[~2012-01-30 16:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 6:39 [PATCH] Prevent 'error' from being tail-called, for better diagnostics Mark H Weaver
2012-01-30 11:05 ` Andy Wingo
2012-01-30 16:32 ` Mark H Weaver [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8762fti22f.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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.
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).