From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Text collation
Date: Sun, 22 Oct 2006 19:01:32 -0700 [thread overview]
Message-ID: <877iyrbxj7.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87r6x0qjyy.fsf@laas.fr> (Ludovic Courtès's message of "Sun, 22 Oct 2006 20:33:09 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
> On IRC, Rob identified a number of issues with this approach:
>
> * It would be the first `ice-9' module that does a `dynamic-link', so
> we may want to think twice before doing it.
>
> * The C programmer willing to use those functions would have to link
> against `libguile-i18n' additionally.
Yes, the main question is to what extent we want people coding in C to
have to link aginst libraries other than -lguile. Of course, this is
already the case for some of the SRFIs.
> There's another (small) issue:
>
> * The online help is a bit confused because the doc of the i18n.c
> functions is include in libguile's `guile-procedure.txt'. Thus,
> `(help make-locale)' always works, even when `(ice-9 i18n)' is not
> loaded.
Perhaps that's something we'll eventually want to fix in the
documentation system, but a really simple approach might be to just
mention the required module in the documentation for each function.
> While I agree that this practically precludes use of those functions
> by C programmers (as is the case for those SRFIs that are
> implemented in C)
Actually, if I understand you correctly, this isn't the case. The
SRFIs (which provide C interfaces) are definitely intended for use by
C programmers. The programmers just have to make sure to include the
correct -lguile-srfi-* for the SRFI in question.
Although I'm not sure it's a great idea, one other possibility would
be to put the C code in libguile, and to provide a C init function,
called from init.c, that doesn't do anything more than publish a
scheme-side init function that can handle the full initialization
later.
Then the startup process should be relatively unaffected, and
ice-9/i18n.scm would just do something like this:
(define-module (ice-9 i18n) ...)
(scm-init-i18n)
This would avoid the need to make it possible to use dynamic-link for
items that are already in libguile. Of course, whether or not the
approach is a good idea is a different question.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-10-23 2:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 9:23 Text collation Ludovic Courtès
2006-09-19 22:38 ` Kevin Ryde
2006-10-22 18:33 ` Ludovic Courtès
2006-10-23 2:01 ` Rob Browning [this message]
2006-10-23 7:56 ` Ludovic Courtès
2006-10-24 8:37 ` Rob Browning
2006-10-25 8:16 ` Ludovic Courtès
2006-10-25 8:46 ` Rob Browning
2006-10-25 18:40 ` Neil Jerram
2006-10-25 19:55 ` Rob Browning
2006-10-26 8:47 ` Ludovic Courtès
2006-11-09 7:44 ` Ludovic Courtès
2006-11-09 17:43 ` Rob Browning
2006-11-10 13:39 ` Ludovic Courtès
2006-11-11 15:17 ` Neil Jerram
2006-11-20 13:24 ` Ludovic Courtès
2006-11-21 22:03 ` Neil Jerram
2006-11-22 13:38 ` Ludovic Courtès
2006-10-25 18:43 ` Neil Jerram
2006-10-25 19:31 ` Rob Browning
2006-10-25 18:33 ` Neil Jerram
2006-10-26 8:39 ` Ludovic Courtès
2006-11-29 23:08 ` Kevin Ryde
2006-11-30 15:19 ` Ludovic Courtès
2006-12-02 21:56 ` Kevin Ryde
2006-12-04 9:01 ` Ludovic Courtès
2006-12-05 0:20 ` Kevin Ryde
2006-12-05 18:42 ` Carl Witty
2006-12-05 20:41 ` Kevin Ryde
2006-12-05 22:29 ` Carl Witty
2006-12-05 0:38 ` Kevin Ryde
2006-12-02 22:02 ` Kevin Ryde
2006-12-10 12:30 ` Ludovic Courtès
2006-12-11 22:32 ` Kevin Ryde
2006-12-12 8:38 ` Ludovic Courtès
2006-12-12 20:04 ` Kevin Ryde
2006-12-13 9:41 ` Ludovic Courtès
2006-12-31 17:10 ` Neil Jerram
2006-12-15 20:52 ` Kevin Ryde
2006-12-12 19:05 ` Kevin Ryde
2006-12-13 9:14 ` Ludovic Courtès
2006-12-12 19:16 ` Kevin Ryde
2006-12-13 9:20 ` Ludovic Courtès
2006-12-12 21:37 ` Kevin Ryde
2006-12-13 9:28 ` Ludovic Courtès
2006-12-13 20:10 ` Kevin Ryde
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=877iyrbxj7.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.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).