From: Mark H Weaver <mhw@netris.org>
To: Andy Wingo <wingo@pobox.com>
Cc: Zefram <zefram@fysh.org>, 16357@debbugs.gnu.org, guile-devel@gnu.org
Subject: bug#16357: insufficient print abbreviation in error messages
Date: Thu, 23 Jun 2016 12:57:17 -0400 [thread overview]
Message-ID: <87lh1vrggi.fsf__48895.4000328251$1466701684$gmane$org@netris.org> (raw)
In-Reply-To: <87ziqezqg5.fsf@pobox.com> (Andy Wingo's message of "Tue, 21 Jun 2016 14:17:30 +0200")
Andy Wingo <wingo@pobox.com> writes:
> Or, we could use print states. But print states are not so great and
> ideally we would remove them eventually.
We will need print states, or something like them, to support writing
cyclic data structures as required by R7RS.
Mark
next prev parent reply other threads:[~2016-06-23 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 23:00 bug#16357: insufficient print abbreviation in error messages Zefram
2016-06-21 12:17 ` Andy Wingo
2016-06-21 12:38 ` Zefram
2016-06-21 15:10 ` Andy Wingo
2016-06-23 16:57 ` Mark H Weaver [this message]
[not found] ` <87lh1vrggi.fsf@netris.org>
2016-06-23 17:59 ` Andy Wingo
2016-06-26 1:05 ` Mark H Weaver
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='87lh1vrggi.fsf__48895.4000328251$1466701684$gmane$org@netris.org' \
--to=mhw@netris.org \
--cc=16357@debbugs.gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
--cc=zefram@fysh.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).