From: Aleksandar Sandic <asflin@gmx.de>
To: guile-user@gnu.org
Subject: [ANN] guile-msgpack: MessagePack for GNU Guile (+ help needed)
Date: Thu, 20 Sep 2018 13:15:24 +0200 [thread overview]
Message-ID: <1775809.DTpK0xyCCj@aleksandar-ixtreme-m5740> (raw)
I have renamed `pack!` and `unpack!` to `pack-to` and `unpack-from`,
following the advice about not using the exclamation mark suffix with side
effects regarding ports. I have also changed the order of arguments so the
first argument to `pack-to` is the port and the rest is an arbitrary number of
objects to pack.
(pack-to (current-output-port) 2 3 "hello")
I think this also rolls better off the tongue: pack to the current output port
2, 3 and "hello".
next reply other threads:[~2018-09-20 11:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 11:15 Aleksandar Sandic [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-20 11:24 [ANN] guile-msgpack: MessagePack for GNU Guile (+ help needed) Aleksandar Sandic
2018-09-19 12:33 HiPhish
2018-09-19 13:29 ` Thompson, David
2018-09-19 14:06 ` HiPhish
2018-09-19 14:12 ` John Cowan
2018-09-19 23:32 ` HiPhish
2018-09-20 1:44 ` John Cowan
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=1775809.DTpK0xyCCj@aleksandar-ixtreme-m5740 \
--to=asflin@gmx.de \
--cc=guile-user@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).