unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Broken Backtraces, and Part of a Solution
Date: Wed, 18 Apr 2012 18:36:06 -0700	[thread overview]
Message-ID: <87sjg0y03d.fsf@pobox.com> (raw)
In-Reply-To: <CA+U71=Mdm9Sc3R_+hB3kL-BRFHqmi3SX40uYOipg6gWBUuQfoQ@mail.gmail.com> (Noah Lavine's message of "Wed, 18 Apr 2012 21:08:05 -0400")

On Wed 18 Apr 2012 18:08, Noah Lavine <noah.b.lavine@gmail.com> writes:

>> We need to change to default to consider generic objects as
>> eq?-compared prompt tags.
>
> I agree, but you still couldn't use procedures or integers as prompt
> tags if you wanted make-stack to work, because those are special
> cases.

Yeah, but the whole point of prompt tags is that you can make a new one
and know that it is eq?-unique, which is not the case for integers.  So
integers are not in the general case.  It seems useful to add procedures
as a special case too, no?

> That's why I thought of just changing the interface to make-stack to
> specify what you want - it's such a weird restriction that someone
> could be bitten by it and have a lot of trouble tracking it down. And
> because an argument can mean three different things, code that uses
> make-stack is hard to understand (or at least it was for me).

It's something of a nasty interface, I agree.  But it's been around for
a long time; if we can make a minimal change, we should, it seems to me.

Want to make a patch?

Regards,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2012-04-19  1:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-19  0:02 Broken Backtraces, and Part of a Solution Noah Lavine
2012-04-19  0:13 ` Noah Lavine
2012-04-19  0:56 ` Andy Wingo
2012-04-19  1:08   ` Noah Lavine
2012-04-19  1:36     ` Andy Wingo [this message]
2012-04-19  2:13       ` Noah Lavine
2012-04-20  2:47         ` Noah Lavine
2012-04-20 14:13           ` Andy Wingo
2012-04-22 10:53           ` Ludovic Courtès
2012-04-24  1:42             ` Noah Lavine
2012-04-24 16:58               ` Ludovic Courtès

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=87sjg0y03d.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=noah.b.lavine@gmail.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).