From: Neil Jerram <neil@ossau.uklinux.net>
Subject: Ditching (debug-enable 'backwards) ?
Date: 27 Oct 2002 13:04:41 +0000 [thread overview]
Message-ID: <m3znt0dod2.fsf@laruns.ossau.uklinux.net> (raw)
Does anyone use (debug-enable 'backwards) and have a good reason for
keeping it?
In my view, it makes documenting the debugger harder, is likely to
introduce bugs in the debugger code (if there aren't any there
already), and is simply pointless, so I propose to get rid of it.
(With deprecation, of course ...)
(Cf. the recent discussion on options on gnucash-devel. I'd say this
is a classic example of a pointless option whose only rationale is
that someone wanted to avoid making a decision.)
Neil
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-10-27 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 13:04 Neil Jerram [this message]
2002-11-03 17:41 ` Ditching (debug-enable 'backwards) ? Marius Vollmer
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=m3znt0dod2.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).