From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: Guile-Devel <guile-devel@gnu.org>
Subject: Re: Text collation
Date: Mon, 23 Oct 2006 09:56:20 +0200 [thread overview]
Message-ID: <87wt6rxy6z.fsf@laas.fr> (raw)
In-Reply-To: <877iyrbxj7.fsf@raven.defaultvalue.org> (Rob Browning's message of "Sun, 22 Oct 2006 19:01:32 -0700")
Hi,
Rob Browning <rlb@defaultvalue.org> writes:
> ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
>> 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.
I don't think this is actually the case: there are currently 4 shared
libraries in the `srfi' directory, but none of them is documented in the
manual and the C functions they export are not mentioned either (that's
what I meant by "practically preclude": it's technically possible to use
them but it's not documented).
I would expect it to be done on purpose: For instance, the contents of
`libguile-srfi-srfi-1' changed noticeably as some functions were
rewritten in C and this is not something we want users to be aware of.
> 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)
Yes, I'm open to that if we consider it a better option than having
another shared lib.
The issue, IMO, is that this is not very "scalable" either: we still end
up adding one function call in `scm_i_init_guile ()' that systematically
gets in the way.
> 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.
Right. What I had in mind was to have, say, `(dynamic-link)' (with no
arguments) translate to `lt_dlopen (NULL)', so that we could access
symbols contained within the executable. Now, I'm not sure this would
work in all cases, for instance when the executable is not `guile'
itself.
Thanks,
Ludovic.
_______________________________________________
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 7:56 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
2006-10-23 7:56 ` Ludovic Courtès [this message]
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=87wt6rxy6z.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--cc=guile-devel@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).