unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: Peter TB Brett <peter@peter-b.co.uk>
Cc: guile-user@gnu.org
Subject: Re: A question about scm_{to,from}_locale_string()
Date: Sun, 12 Jun 2011 11:28:11 +0200	[thread overview]
Message-ID: <87wrgrv1p0.fsf@ambire.localdomain> (raw)
In-Reply-To: <m3zklnmsq8.fsf@harrington.peter-b.co.uk> (Peter TB Brett's message of "Sun, 12 Jun 2011 08:09:03 +0100")

() Peter TB Brett <peter@peter-b.co.uk>
() Sun, 12 Jun 2011 08:09:03 +0100

   I've added a configure check that defines
   scm_{to,from}_utf8_string to scm_{to,from}_locale_string if
   the former isn't available in libguile.  Seems to work okay.

   Obviously there are some cases where we still use the locale
   functions explicitly, e.g. parsing command-line arguments.

Probably sooner or later it behooves us (clients of libguile)
to hold a libguile "portability summit", where common bits of
autoconfigury, shimming, etc can be actively pooled, refactored
and (hopefully) incorporated into a time-saving tarball.

In this way, stuff like the autoconf check you mention, and
stuff like Autogen's or Serveez's C shims can be centrally
maintained and not re-invented time and time again.

____________________________________________________________________
[0] or "pit of despair", depending on your mood :-/



  reply	other threads:[~2011-06-12  9:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11 10:13 A question about scm_{to,from}_locale_string() Peter TB Brett
2011-06-11 14:19 ` Ludovic Courtès
2011-06-12  7:09   ` Peter TB Brett
2011-06-12  9:28     ` Thien-Thi Nguyen [this message]
2011-06-12  9:46       ` Peter TB Brett
2011-06-12 16:24         ` Thien-Thi Nguyen

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=87wrgrv1p0.fsf@ambire.localdomain \
    --to=ttn@gnuvola.org \
    --cc=guile-user@gnu.org \
    --cc=peter@peter-b.co.uk \
    /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).