From: Bruno Haible <bruno@clisp.org>
To: Miguel <rosen644835@gmail.com>
Cc: guile-devel@gnu.org, bug-gettext@gnu.org
Subject: Re: Libgettextpo wrapper for Guile
Date: Sun, 05 May 2019 20:45:40 +0200 [thread overview]
Message-ID: <1721811.yzKoui1vof@omega> (raw)
In-Reply-To: <20190505183409.4a2b8a3e@gmail.com>
Hi Miguel,
> an external project would be useful anyway as
> does not require a version update of neither Gettext nor Guile to start
> using it
A separate project also means an independent release cycle.
How are other Guile bindings organized?
- guile-cairo separate project https://www.nongnu.org/guile-cairo/
- guile-gnome separate project https://www.gnu.org/software/guile-gnome/
- guile-git separate project https://gitlab.com/guile-git/guile-git
- libgccjit separate project https://savannah.nongnu.org/projects/gccjit-guile/
- guile-gnutls at gnutls https://www.gnutls.org/manual/gnutls-guile.html
- zeromq at zeromq http://zeromq.org/bindings:guile-binding
- gmp part of guile https://gmplib.org/manual/Language-Bindings.html
The majority seems to have chosen to be available as separate project.
> I think the choice should have more to do with Gettext's desire as a
> project to extend its code base in Guile in the future, as the Guile
> library could be the foundation for new tools, or to keep C as the main
> code base
There are no plans to use a different implementation language for
PO file manipulations. With the existing code base as a start, it
is not much harder to code new functionality in C than it would be
to code it in Python, guile, Java, or other languages.
Gettext needs a different implementation language in other areas -
such as extracting relevant information from HTML pages - and is
using POSIX sh for this purpose. It's a balance between language
features, portability, and ease of installation / minimization of
dependencies.
Bruno
next prev parent reply other threads:[~2019-05-05 18:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 22:49 Libgettextpo wrapper for Guile Miguel
[not found] ` <20190505004925.24e650e4-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-05-05 13:45 ` Bruno Haible
2019-05-05 16:34 ` Miguel
2019-05-05 18:45 ` Bruno Haible [this message]
2019-05-05 23:04 ` amirouche
2019-05-08 14:33 ` Miguel
2019-05-08 14:32 ` Miguel
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=1721811.yzKoui1vof@omega \
--to=bruno@clisp.org \
--cc=bug-gettext@gnu.org \
--cc=guile-devel@gnu.org \
--cc=rosen644835@gmail.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).