From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Guile Development <guile-devel@gnu.org>,
Guile Users <guile-user@gnu.org>
Subject: Re: Ditching (debug-enable 'backwards) ?
Date: 04 Nov 2002 22:42:33 +0100 [thread overview]
Message-ID: <87pttl8112.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3fzuhxfx4.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> To be more precise, what I don't like about 'backwards is that it
> changes how the displayed frames are _numbered_:
Well, that sounds like the wrong thing to do wrong. I thought that
'backwards would just print the same lines as the forward display,
only in reverse order. There shouldn't really be any more difference
between the two, no?
> I have no objection to frames appearing in reverse order, but I prefer
> that they were then _numbered_ like this (artist's impression):
Yes, exactly my opinion as well.
> Marius> Is that so? The 'backwards' option should only matter
> Marius> during display and we already have that code, right?
>
> We do, but as we develop debugging tools further, I'd prefer not to
> have the call everywhere that converts the frame number as typed by
> the user to the correct stack index. It's so easy to leave this call
> out somewhere, and easy not to notice the omission.
Yes. We should either fix the backwards display then, or disable it
(but leave the code in so that it can be fixed later).
> As a further point, is similarity with GDB worth anything here? GDB
> numbers frames so that frame 0 is the innermost, so perhaps Guile
> should do that too. (GDB's direction also has the advantage that "up"
> for frames coincides with "up" for frame numbers.)
GDB's convention sounds more useful to me. The innermost frame is
more important than the outermost one and should get a simple index.
With our convention, you have to know how many frames there are before
being able to name the innermost one or any frame relative to it.
Is it possible to fix this without creating a lot of confusion?
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2002-11-04 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 13:04 Ditching (debug-enable 'backwards) ? Neil Jerram
2002-11-03 17:41 ` Marius Vollmer
2002-11-04 20:01 ` Neil Jerram
2002-11-04 21:42 ` Marius Vollmer [this message]
2002-11-05 23:13 ` Neil Jerram
2002-11-06 12:50 ` Mikael Djurfeldt
2002-11-06 12:49 ` Mikael Djurfeldt
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=87pttl8112.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@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.
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).