unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Text collation
Date: Wed, 25 Oct 2006 01:46:02 -0700	[thread overview]
Message-ID: <87mz7kokad.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87slhclsj9.fsf@laas.fr> (Ludovic Courtès's message of "Wed, 25 Oct 2006 10:16:10 +0200")

ludovic.courtes@laas.fr (Ludovic Courtès) writes:

> No, it doesn't work.  In the latest `guile-reader', I have a couple of
> modules that do (part of) what the Awk script in `libguile' does:
> parsing the output of `cpp -DSCM_MAGIC_SNARF'.  I'd be in favor of
> integrating such an approach in Guile core eventually.

Yes.  It would be nice to have a more comprehensive solution for
documentation, one that can be used both internally and externally.

> Personally, I would like Guile "core" to be much more modular than what
> it is now.  I believe many things in what we call "Guile core" are there
> just because we want them to be part of the "standard Guile library",
> but they certainly to not comprise the "core" or "kernel" of Guile.  For
> instance, I believe the Gettext-related functions ought to be
> distributed with Guile core but as a separate module.  Same for
> SRFI-1[43].  Not to mention the bits and pieces that are in `boot-9' and
> that happen to be visible to everyone.  ;-)

I don't really disagree.  In particular, I think this is something we
should definitely consider as we examine R6RS.

> Now, whether each module should load its own shared library is a
> different issue.  This may depend on the module characteristics:
> size, usefulness, C programmability.  We also have to find a balance
> between lazy initialization (with `dynamic-link') and systematic
> initialization.
>
> Getting back to `(ice-9 i18n)': I'm strongly in favor of keeping this as
> a module; I am more inclined to having it in a separate shared library
> (because it's not useful to everyone) but I wouldn't mind having it in
> `libguile.so'.

I'm somewhat inclined to think that the scheme-side module is a good
idea, though perhaps it begs more general organizational questions.
I'm less certain about whether or not adding small shared library is a
good idea.  However, in both cases, I need to think a bit more.

-- 
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


  reply	other threads:[~2006-10-25  8:46 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
2006-10-24  8:37         ` Rob Browning
2006-10-25  8:16           ` Ludovic Courtès
2006-10-25  8:46             ` Rob Browning [this message]
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=87mz7kokad.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).