This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/5486] nl_langinfo() returns invalid pointer instead of expected empty string
- From: "bugzilla at somabo dot de" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 18 Dec 2007 20:40:23 -0000
- Subject: [Bug libc/5486] nl_langinfo() returns invalid pointer instead of expected empty string
- References: <20071213225007.5486.bugs@daylessday.org>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From bugzilla at somabo dot de 2007-12-18 20:40 -------
We are obviously speaking about a glibc specific addition here. So wtf is that
not handled in a glibc specific function? The standard says clearly that an
invalid value results in an empty string. Also we apparently can only receive a
string here. Because where I live we code our prototypes correct. Now even if
all you guys said were true then we still have an issue here. Any however well
documented glibc specific value is still undefined in any other open/public
documentation. That said it still needs to return an empty string. If you do not
like it then you can do that by simply getting your undocumented union right.
union glibc_fun {
const char string[];
struct more_fun {
const char nul;
union even_more_fun {
int an_unexpected_int_value;
double even_a_double_is_possible;
// and so on
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5486
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.