unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-user <guile-user@gnu.org>
Subject: Re: [announce] released gee--beta--0.2--base-0
Date: Fri, 19 May 2006 14:29:40 +0200	[thread overview]
Message-ID: <87bqtu42q3.fsf@laas.fr> (raw)
In-Reply-To: <IZFFRC$659D4CA0D45EAE2610ED5D035823DD48@poste.it> (Marco Maggi's message of "Wed, 17 May 2006 22:33:12 +0200")

Hi,

"Marco Maggi" <marco.maggi-ipsu@poste.it> writes:

> GEE includes extensions for:
>
> * ASCII armor
> * Endianness conversion
> * GNU Libgcrypt
> * GNU multiple precision arithmetic library (GMP)
> * Multiple Precision Floating-Point Reliable library (MPFR)
> * Multiple Precision Complex Library (MPC)
> * Multiple Precision Floating-Point Interval Library (MPFI)
> * GNU Scientific Library (GSL) (early alpha)
> * GNU Libiconv
> * MHASH, hash algorithms library
> * NETTLE, cryptographic library
> * Libspopc, simple POP3 client
> * OSSP UUID, universally unique identifier library
> * Portable Coroutine Library (PCL) (alpha)
> * URI, Uniform Resource Identifier parser
> * Miscellaneous random numbers generators.

All these bindings look interesting, but why not publish them
independently?  For GNU libraries, the bindings could even be included
upstream I guess, which would be very beneficial to Guile users.

Also, Guile 1.8 uses GMP internally.  Does your set of bindings provide
additional functionalities (I understand that your main goal was
educational)?

Thanks,
Ludovic.


_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user


  reply	other threads:[~2006-05-19 12:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 20:33 [announce] released gee--beta--0.2--base-0 Marco Maggi
2006-05-19 12:29 ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-19 19:30 Marco Maggi

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=87bqtu42q3.fsf@laas.fr \
    --to=ludovic.courtes@laas.fr \
    --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).