From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: frozen!
Date: Wed, 07 Oct 2009 00:25:51 +0200 [thread overview]
Message-ID: <874oqcxiq8.fsf@gnu.org> (raw)
In-Reply-To: 5A852E08-69B5-4133-9B02-485B58B7FE6C@raeburn.org
Ken Raeburn <raeburn@raeburn.org> writes:
> On Oct 6, 2009, at 17:35, Mike Gran wrote:
>> I need to roll back the changes made to i18n.c
>> that made locale-specific case conversion of strings
>> work on GNU but break on Darwin. Locale-specific
>> case conversion of strings works, but only when
>> the locale is set using setlocale.
>
> Thanks. Though perhaps you could just explicitly test for GNU libc,
> if the glibc structures are stable?
There's no reason why they should be stable, they're internal. Glibc's
<xlocale.h> reads:
--8<---------------cut here---------------start------------->8---
/* Structure for reentrant locale using functions. This is an
(almost) opaque type for the user level programs. The file and
this data structure is not standardized. Don't rely on it. It can
go away without warning. */
typedef struct __locale_struct
--8<---------------cut here---------------end--------------->8---
Maybe, until a better solution is found we could use:
AC_CHECK_MEMBER([struct __locale_struct.__name] ...)
But we should aim for a more robust solution.
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-10-06 22:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 19:47 frozen! Andy Wingo
2009-10-06 21:00 ` frozen! Neil Jerram
2009-10-06 21:35 ` frozen! Mike Gran
2009-10-06 21:45 ` frozen! Ludovic Courtès
2009-10-06 22:07 ` frozen! Ken Raeburn
2009-10-06 22:25 ` Ludovic Courtès [this message]
2009-10-09 7:54 ` frozen! Ken Raeburn
2009-10-10 14:43 ` frozen! Ken Raeburn
2009-10-12 13:56 ` frozen! Mike Gran
2009-10-12 17:31 ` setbinary Ludovic Courtès
2009-10-18 10:27 ` frozen! Andy Wingo
2009-10-06 21:49 ` frozen! Ludovic Courtès
2009-10-18 10:33 ` frozen! Andy Wingo
2009-10-18 13:54 ` frozen! Ludovic Courtès
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=874oqcxiq8.fsf@gnu.org \
--to=ludo@gnu.org \
--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).