From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Romel Sandoval <romel@lavabit.com>
Cc: guile-user@gnu.org
Subject: Re: Guile base64
Date: Sun, 05 Sep 2010 23:58:16 +0200 [thread overview]
Message-ID: <87zkvvsvif.fsf@ambire.localdomain> (raw)
In-Reply-To: <1283544958.4017.4.camel@romel-compaq> (Romel Sandoval's message of "Fri, 03 Sep 2010 15:15:58 -0500")
() Romel Sandoval <romel@lavabit.com>
() Fri, 03 Sep 2010 15:15:58 -0500
Do you think any of mentioned implementations should be
included with Guile 2.0 or it's better to keep it apart?
Probably next week (2010-09-13 onward) i can find some time to add
(ice-9 base64) from Guile 1.4.x. However, that implementation uses
‘(srfi srfi-56) read-byte’, which is not available in Guile 2.
Could someone suggest a replacement?
next prev parent reply other threads:[~2010-09-05 21:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 18:10 Guile base64 Romel Sandoval
2010-09-02 8:12 ` Ludovic Courtès
2010-09-02 18:49 ` Andy Wingo
2010-09-02 23:34 ` Andreas Rottmann
2010-09-03 20:15 ` Romel Sandoval
2010-09-05 21:58 ` Thien-Thi Nguyen [this message]
2010-09-05 22:47 ` Ludovic Courtès
2010-09-06 9:39 ` Thien-Thi Nguyen
2010-09-06 9:59 ` Andy Wingo
2010-09-28 12:48 ` Thien-Thi Nguyen
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=87zkvvsvif.fsf@ambire.localdomain \
--to=ttn@gnuvola.org \
--cc=guile-user@gnu.org \
--cc=romel@lavabit.com \
/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).