From: "Marco Maggi" <marco.maggi-ipsu@poste.it>
Subject: Re: [announce] released gee--beta--0.2--base-0
Date: Fri, 19 May 2006 20:30:20 +0100 [thread overview]
Message-ID: <IZJ26K$798DB35C8841462BF3A9383DF59B9AAB@poste.it> (raw)
"ludovic.courtes@laas.fr" wrote:
>but why not publish them independently?
All of them depend on the same (small) library,
the one under the 'lib' subdirectory; additionally:
all the pipe port extensions depend on the same
library (the one under the 'ende' directory), and
that one does not depend on Guile: it can be used
in other C libraries.
In this situation, and being in the early stages of
development, having a single package makes it easy for
me to automatically test all the code at each change
in the common code.
However I'm not sure that 15 packages (with dependeces)
would make it easy for the Guile user.
>For GNU libraries, the bindings could even be
>included upstream I guess, which would be very
>beneficial to Guile users.
Ideally this could happen. And I think that, especially
for some of the (non GNU) math extensions, it would
make testing easier for the upstream develpers, too.
Chi vivrà, vedrà...
>Also, Guile 1.8 uses GMP internally. Does your
>set of bindings provide additional functionalities
It exposes integer functions not exposed by Guile,
like the number theoretic ones; it also exposes
MPF functions (but I have to review that code).
--
Marco Maggi
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next reply other threads:[~2006-05-19 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-19 19:30 Marco Maggi [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-17 20:33 [announce] released gee--beta--0.2--base-0 Marco Maggi
2006-05-19 12:29 ` Ludovic Courtès
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='IZJ26K$798DB35C8841462BF3A9383DF59B9AAB@poste.it' \
--to=marco.maggi-ipsu@poste.it \
/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).