public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/15459] RFE: Add |localeconv_l()| to allow porting of FreeBSD/OSX applications... Date: Tue, 14 May 2013 17:02:00 -0000 [thread overview] Message-ID: <bug-15459-131-uPgMRqCv0y@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15459-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15459 --- Comment #4 from Rich Felker <bugdal at aerifal dot cx> 2013-05-14 17:02:26 UTC --- By harmful, I meant harmful to portability and/or application simplicity. If there's already a simple, portable way to do something that doesn't have excessive cost, adding a second way to do it means an application will take one of three paths: 1. Using the portable way and ignoring the availability of the non-portable one. 2. Adding configure checks and #ifdefs to use the new way optionally. 3. Using the new non-portable way unconditionally. Of these, I would consider option 1 the best for applications, since it minimizes complexity and maximizes compatibility. Option 2 risks bitrot in the code path that's not taken on the developers' systems. Option 3 means the program can only be used on BSD and GNU systems. Now if GNU is the only major system lacking this interface, or if other vendors are equally interested and willing to add it, then a path towards standardization, with applications using option 2 above and gradually phasing out the old option as implementations adopt the new interface(s), would be very reasonable. Actually glibc and BSD already have a number of *_l functions outside the ones standardized in POSIX 2008, so if this is the approach you want to take, it would be good to see if the committee is opposed to adding them all in Issue 8, and if not, doing the work to get them added (which basically amounts to writing the proposed text for the standard). -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next prev parent reply other threads:[~2013-05-14 17:02 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-05-11 1:18 [Bug libc/15459] New: " roland.mainz at nrubsig dot org 2013-05-11 1:27 ` [Bug libc/15459] " roland.mainz at nrubsig dot org 2013-05-11 3:26 ` carlos at redhat dot com 2013-05-11 23:44 ` bugdal at aerifal dot cx 2013-05-14 14:17 ` carlos at redhat dot com 2013-05-14 17:02 ` bugdal at aerifal dot cx [this message] 2013-05-14 19:02 ` carlos at redhat dot com 2013-05-14 21:50 ` roland.mainz at nrubsig dot org 2013-05-14 22:07 ` bugdal at aerifal dot cx 2013-06-16 4:30 ` bugdal at aerifal dot cx 2013-07-12 1:47 ` carlos at redhat dot com 2013-07-12 2:44 ` wendlin1974 at gmail dot com 2013-07-12 2:54 ` wendlin1974 at gmail dot com 2013-07-12 3:20 ` bugdal at aerifal dot cx 2013-07-12 5:25 ` jakub at redhat dot com 2014-06-13 13:24 ` fweimer at redhat dot com 2015-08-27 22:14 ` [Bug locale/15459] " jsm28 at gcc dot gnu.org
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=bug-15459-131-uPgMRqCv0y@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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).