unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Nala Ginrut <nalaginrut@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: [Request] How about adding with-locale?
Date: Sat, 24 Mar 2012 13:56:43 -0400	[thread overview]
Message-ID: <87pqc1naqs.fsf@netris.org> (raw)
In-Reply-To: <CAPjoZoe5i+Uo0ZYV9dxWi6jDMYfk6ZsZZOU69196a+Xz=J2p=A@mail.gmail.com> (Nala Ginrut's message of "Sat, 24 Mar 2012 20:42:48 +0800")

Nala Ginrut <nalaginrut@gmail.com> writes:
> According to our talking on IRC. I dropped locale specific procedure
> setlocale in my code. I choose (web http) write-date instead. 
> And my conclusion is to avoid locale specific things in multi-thread
> context.

It's okay to use locale-dependent operations in a multi-thread program,
as long as you use only one locale for the entire process.

Even in a single-thread program, locale-dependent operations are not
appropriate for protocol use, IMO anyway.  For security reasons,
protocol code should be as simple as possible, but locale-sensitive code
tends to be much more complex.  Also, it seems to me that locale
formatters/parsers are designed for _human_ interfaces, which have a
fundamentally different set of requirements than a protocol interface.

   Regards,
     Mark



  reply	other threads:[~2012-03-24 17:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24  4:37 [Request] How about adding with-locale? Nala Ginrut
2012-03-24  4:43 ` Nala Ginrut
2012-03-24  6:54   ` Mark H Weaver
2012-03-24  8:45     ` Nala Ginrut
2012-03-24 10:24       ` Mark H Weaver
2012-03-24 12:42         ` Nala Ginrut
2012-03-24 17:56           ` Mark H Weaver [this message]
2012-04-02 15:27     ` Ludovic Courtès
2012-04-02 16:28       ` Nala Ginrut
2012-04-02 15:29 ` 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=87pqc1naqs.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=nalaginrut@gmail.com \
    /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).