From 9250d75a95295dd09aed581838f0b619792911cd Mon Sep 17 00:00:00 2001 From: Jarkko Hietaniemi Date: Sat, 29 Dec 2001 18:28:36 +0000 Subject: [PATCH] Give up on serious testing of langinfo(). Leave the old code in place, though. p4raw-id: //depot/perl@13937 --- ext/I18N/Langinfo/Langinfo.t | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/ext/I18N/Langinfo/Langinfo.t b/ext/I18N/Langinfo/Langinfo.t index 2f5172d..7c6089a 100644 --- a/ext/I18N/Langinfo/Langinfo.t +++ b/ext/I18N/Langinfo/Langinfo.t @@ -17,6 +17,21 @@ use POSIX qw(setlocale LC_ALL); setlocale(LC_ALL, $ENV{LC_ALL} = $ENV{LANG} = "C"); +print "1..1\n"; # We loaded okay. That's about all we can hope for. +print "ok 1\n"; +exit(0); +# Background: the langinfo() (in C known as nl_langinfo()) interface +# is supposed a to be a portable way to fetch various language dependent +# constants like "the first day of the week" or "the decimal separator". +# Give a portable (numeric) constant, get back a language-specific string. +# That's a comforting fantasy. Now tune in for blunt reality: +# vendors seem to have implemented for those constants whatever they +# felt like defining. The UNIX standard says that one should have +# the RADIXCHAR constant for the decimal separator. Not so for many +# Linux and BSD implementations. One should have the CODESET constant +# for returning the current codeset (say, ISO 8859-1). Not so. +# --jhi + my %want = ( ABDAY_1 => "Sun", -- 2.7.4