From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Locale bikeshed time
Date: Sat, 26 Jul 2014 05:25:16 -0400 [thread overview]
Message-ID: <20140726092516.GL4038@brightrain.aerifal.cx> (raw)
In-Reply-To: <1406365616.6438.98.camel@eris.loria.fr>
On Sat, Jul 26, 2014 at 11:06:56AM +0200, Jens Gustedt wrote:
> Am Samstag, den 26.07.2014, 04:03 -0400 schrieb Rich Felker:
> > The problem is that the vast majority of actual printing and parsing
> > of floating point numbers is for interchange purposes, not mere visual
> > pretty-printing,
>
> do you have statistics that support that claim?
Anecdotes, yes; statistics, no. Some examples that come to mind
immediately:
- Anything JSON
- Text-based 3D model files
- Subtitle file timings
- Video framerates, aspect ratios, etc.
- Input files for scientific and mathematical computing.
...
> printing that is really concerned in interchange, should just use the
> %a formats. All other formats are intended for human readability.
In an ideal world, yes, people would use %a. In practice I don't think
I've ever seen it used. :( And the radix point affects %a anyway,
which is rather nonsensical, since there's definitely no cultural
convention for commas to be used as radix points in hex floats.
> > This goes back to the question about modern versus old tradition.
> > Alternate radix points are a cultural convention that's (seemingly,
> > hopefully) on the way out due to computers and information
> > interchange. Maybe in some sense this is cultural imperialism (or just
> > globalization or whatnot)
>
> +1 for imperialism
Call it what you like, but lack of a variable LC_NUMERIC has been part
of the proposed locale design since the beginning. This isn't
something new I'm springing now. The radix point in LC_NUMERIC is also
probably the single most-hated part of locale by members of the
community who objected to musl having any sort of locale support at
all.
Rich
next prev parent reply other threads:[~2014-07-26 9:25 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 18:49 Rich Felker
2014-07-22 20:10 ` u-igbb
2014-07-22 20:35 ` Rich Felker
2014-07-23 9:50 ` u-igbb
2014-07-23 16:39 ` Rich Felker
2014-07-23 19:25 ` u-igbb
2014-07-23 21:01 ` Rich Felker
2014-07-24 15:35 ` u-igbb
2014-07-24 16:01 ` Rich Felker
2014-07-24 19:24 ` u-igbb
2014-07-24 20:15 ` u-igbb
2014-07-24 22:02 ` Rich Felker
2014-07-25 9:06 ` u-igbb
2014-07-25 20:15 ` u-igbb
2014-07-25 22:32 ` Rich Felker
2014-07-26 7:25 ` u-igbb
2014-07-26 8:03 ` Rich Felker
2014-07-26 9:06 ` Jens Gustedt
2014-07-26 9:25 ` Rich Felker [this message]
2014-07-26 9:38 ` u-igbb
2014-07-26 17:47 ` Szabolcs Nagy
2014-07-26 18:23 ` Rich Felker
2014-07-26 18:59 ` u-igbb
2014-07-26 19:14 ` Rich Felker
2014-07-26 18:56 ` u-igbb
2014-07-26 19:30 ` Rich Felker
2014-07-27 7:28 ` u-igbb
2014-07-26 20:43 ` Rich Felker
2014-07-27 7:51 ` u-igbb
2014-07-27 8:00 ` Rich Felker
2014-07-27 8:24 ` u-igbb
2014-07-23 23:22 ` writeonce
2014-07-23 23:38 ` Rich Felker
2014-07-24 1:07 ` writeonce
2014-07-24 1:57 ` Rich Felker
2014-07-24 2:16 ` writeonce
2014-07-24 2:24 ` Rich Felker
2014-07-24 2:59 ` writeonce
2014-07-22 20:17 ` Laurent Bercot
2014-07-22 20:36 ` Rich Felker
2014-07-23 22:03 ` Laurent Bercot
2014-07-23 22:12 ` Rich Felker
2014-07-24 15:38 ` u-igbb
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140726092516.GL4038@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).