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: 03 Nov 2002 18:41:02 +0100 [thread overview]
Message-ID: <8765veblg1.fsf@zagadka.ping.de> (raw)
In-Reply-To: <m3znt0dod2.fsf@laruns.ossau.uklinux.net>
Neil Jerram <neil@ossau.uklinux.net> writes:
> Does anyone use (debug-enable 'backwards) and have a good reason for
> keeping it?
Hmm. I'd say we should only remove it when there is significant cost
associated with it. Since we already have it, we might as well keep
it. Maybe it will make someone happy. :-)
> In my view, it makes documenting the debugger harder,
It would good enough to just document the default case and only
mention somewhere that the backtrace can also be displayed backwards
but that the documentation assumes that it is not being done.
> is likely to introduce bugs in the debugger code (if there aren't
> any there already),
Is that so? The 'backwards' option should only matter during display
and we already have that code, right?
On the other hand, if you need to write new display code for the
debugger and the backwards option makes that significantly harder, I'd
say it is OK to remove it.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-11-03 17:41 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 [this message]
2002-11-04 20:01 ` Neil Jerram
2002-11-04 21:42 ` Marius Vollmer
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=8765veblg1.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).