From: daniel.llorens@bluewin.ch
To: guile-devel@gnu.org
Subject: (unknown)
Date: Wed, 8 Feb 2017 10:15:39 +0100 [thread overview]
Message-ID: <20170208091540.38123-1-daniel.llorens@bluewin.ch> (raw)
In-Reply-To: <Fix array corner cases in truncated-print>
This (I think last) patch for truncated-print adds support for
bitvectors and also makes sure to print the correct array print prefix
when it's not trivial (non-zero base indices or zero dimensions). For
this I need to pull out a piece of scm_i_print_array as
array-print-prefix.
next parent reply other threads:[~2017-02-08 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Fix array corner cases in truncated-print>
2017-02-08 9:15 ` daniel.llorens [this message]
2017-02-08 9:15 ` [PATCH] Fix more corner cases in truncated-print daniel.llorens
2017-02-03 12:51 (unknown) daniel.llorens
-- strict thread matches above, loose matches on Subject: below --
2013-04-08 2:50 (unknown) dsmich
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=20170208091540.38123-1-daniel.llorens@bluewin.ch \
--to=daniel.llorens@bluewin.ch \
--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).