From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-sources@gnu.org
Cc: guile-user@gnu.org
Subject: SNUGGLE 0.3 available
Date: Sun, 16 Jun 2013 12:11:37 +0200 [thread overview]
Message-ID: <87bo7674bq.fsf@zigzag.favinet> (raw)
[-- Attachment #1: Type: text/plain, Size: 802 bytes --]
release notes:
New header, gifted from Guile-SDL, modified to
waste memory less for Guile versions prior to 1.8.
thi
README excerpt:
SNUGGLE: Neutralize Uncharacteristically Grotesque GUILE Library Entropy!
This package is for programmers frustrated with libguile API churn.
It provides a command-line program that helps manange a (very thin)
abstraction layer between the installed libguile API and your program.
NEWS excerpt:
- 0.3 | 2013-06-16
- new header: mkhash.h
This provides macro ‘MAKE_HASH_TABLE’.
- bootstrap tools upgraded
- GNU Automake 1.13.2
tarball, etc, in dir:
http://www.gnuvola.org/software/snuggle/
atom feed:
http://www.gnuvola.org/NEWS.atom
--
Thien-Thi Nguyen
GPG key: 4C807502
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2013-06-16 10:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87bo7674bq.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=guile-sources@gnu.org \
--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).