From: Matt Wette <matt.wette@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: guile 3 desires: guile-3-0, and debugging
Date: Wed, 22 Nov 2017 08:08:39 -0800 [thread overview]
Message-ID: <BCC042F2-B43A-4C3E-9B1A-1A6DF50E02CD@gmail.com> (raw)
Here are a couple desires:
1) more cases for cond-expand, in case 3.2 has items 3.0 does not (e.g., srfi-199)
2) better debugging.
Maybe I'm not doing it right, but I struggle in this area: I mostly resort to printing.
For example, add scheme level hook, or command arg, to turn off optimization.
next reply other threads:[~2017-11-22 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 16:08 Matt Wette [this message]
2017-11-24 23:42 ` guile 3 desires: guile-3-0, and debugging Christopher Allan Webber
2017-11-25 0:50 ` Matt Wette
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=BCC042F2-B43A-4C3E-9B1A-1A6DF50E02CD@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-devel@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).