[32835] in Perl-Users-Digest
Perl-Users Digest, Issue: 4100 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Dec 24 21:09:34 2013
Date: Tue, 24 Dec 2013 18:09:05 -0800 (PST)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Tue, 24 Dec 2013 Volume: 11 Number: 4100
Today's topics:
Re: Question about language setting <hjp-usenet3@hjp.at>
Re: Question about language setting <rweikusat@mobileactivedefense.com>
Re: Question about language setting <hjp-usenet3@hjp.at>
Re: Question about language setting <dave@invalid.invalid>
Re: tricky stdout <gravitalsun@hotmail.foo>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 23 Dec 2013 23:01:34 +0100
From: "Peter J. Holzer" <hjp-usenet3@hjp.at>
Subject: Re: Question about language setting
Message-Id: <slrnlbhclu.mm3.hjp-usenet3@hrunkner.hjp.at>
On 2013-12-23 15:39, Dave Saville <dave@invalid.invalid> wrote:
> I have a perl script that checks a program's "data base" for
> consistancy.
>
> A German user said it would not run and threw a "Feature bundle 5.0.0"
> not supported from feature.pm. This was because I call Carp.
It would be useful to know where this error occurs. Just "a perl script"
is a bit vague.
I get this error if I write something like
use feature ':5.0.0';
but that is independent of the locale setting. Feature.pm was introduced
in 5.10 and there aren't any feature bundles less than :5.10.
Also, details about the system in question (OS/distribution, perl
version) would also be useful.
> He now says
>
><qoute>
> the perl problem seems to be solved: it's not a problem with
> installation or version. The problem is the setting for "LANG": It has
> to be LANG=en_US.UTF-8 and not LANG=de_DE_EURO which is the standard
> for german!
></quote>
>
> Surely (base) perl modules aren't dependent on language?
>
They shouldn't be. It might be a bug in perl, in the module or in a
system library. Or it might be a bug in your script. It is impossible to
tell with the information you have given.
hp
--
_ | Peter J. Holzer | Fluch der elektronischen Textverarbeitung:
|_|_) | | Man feilt solange an seinen Text um, bis
| | | hjp@hjp.at | die Satzbestandteile des Satzes nicht mehr
__/ | http://www.hjp.at/ | zusammenpat. -- Ralph Babel
------------------------------
Date: Mon, 23 Dec 2013 22:50:30 +0000
From: Rainer Weikusat <rweikusat@mobileactivedefense.com>
Subject: Re: Question about language setting
Message-Id: <87ppon41xl.fsf@sable.mobileactivedefense.com>
"Peter J. Holzer" <hjp-usenet3@hjp.at> writes:
> On 2013-12-23 15:39, Dave Saville <dave@invalid.invalid> wrote:
[...]
>> He now says
>>
>><qoute>
>> the perl problem seems to be solved: it's not a problem with
>> installation or version. The problem is the setting for "LANG": It has
>> to be LANG=en_US.UTF-8 and not LANG=de_DE_EURO which is the standard
>> for german!
>></quote>
>>
>> Surely (base) perl modules aren't dependent on language?
>
> They shouldn't be. It might be a bug in perl, in the module or in a
> system library. Or it might be a bug in your script. It is impossible to
> tell with the information you have given.
Considering the statement from 'the user', this must be something which
causes the behaviour of some perl code to change because it is using a
German locale. Considering what is in a locale definition, this makes
LC_NUMERIC the most likely candidate, especially considering that this
is the only locale-information used as part of version checking (by
Perl_upg_version in util.c).
------------------------------
Date: Tue, 24 Dec 2013 00:14:54 +0100
From: "Peter J. Holzer" <hjp-usenet3@hjp.at>
Subject: Re: Question about language setting
Message-Id: <slrnlbhgvf.3p1.hjp-usenet3@hrunkner.hjp.at>
On 2013-12-23 22:50, Rainer Weikusat <rweikusat@mobileactivedefense.com> wrote:
> "Peter J. Holzer" <hjp-usenet3@hjp.at> writes:
>> On 2013-12-23 15:39, Dave Saville <dave@invalid.invalid> wrote:
>>> He now says
>>>
>>><qoute>
>>> the perl problem seems to be solved: it's not a problem with
>>> installation or version. The problem is the setting for "LANG": It has
>>> to be LANG=en_US.UTF-8 and not LANG=de_DE_EURO which is the standard
>>> for german!
>>></quote>
>>>
>>> Surely (base) perl modules aren't dependent on language?
>>
>> They shouldn't be. It might be a bug in perl, in the module or in a
>> system library. Or it might be a bug in your script. It is impossible to
>> tell with the information you have given.
>
> Considering the statement from 'the user', this must be something which
> causes the behaviour of some perl code to change because it is using a
> German locale. Considering what is in a locale definition, this makes
> LC_NUMERIC the most likely candidate, especially considering that this
> is the only locale-information used as part of version checking (by
> Perl_upg_version in util.c).
Yes, I know. But I couldn't reproduce it. And that's not very
surprising: Many people use perl with a German locale, so it can't be
something generic like "perl doesn't work with a German locale" or "use
feature doesn't work with a German locale". It has to be something more
specific, like a bug in the locale implementation of the user's system
(but Dave hasn't told us what system it is) or the way a certain feature
is used (but Dave hasn't told us anything about his script). But it is
impossible to find out what it is unless Dave volunteers more
information.
hp
--
_ | Peter J. Holzer | Fluch der elektronischen Textverarbeitung:
|_|_) | | Man feilt solange an seinen Text um, bis
| | | hjp@hjp.at | die Satzbestandteile des Satzes nicht mehr
__/ | http://www.hjp.at/ | zusammenpat. -- Ralph Babel
------------------------------
Date: Tue, 24 Dec 2013 10:39:53 +0000 (UTC)
From: "Dave Saville" <dave@invalid.invalid>
Subject: Re: Question about language setting
Message-Id: <fV45K0OBJxbE-pn2-sdWdY9DZjkMK@paddington.bear.den>
On Mon, 23 Dec 2013 23:14:54 UTC, "Peter J. Holzer"
<hjp-usenet3@hjp.at> wrote:
> On 2013-12-23 22:50, Rainer Weikusat <rweikusat@mobileactivedefense.com> wrote:
> > "Peter J. Holzer" <hjp-usenet3@hjp.at> writes:
> >> On 2013-12-23 15:39, Dave Saville <dave@invalid.invalid> wrote:
> >>> He now says
> >>>
> >>><qoute>
> >>> the perl problem seems to be solved: it's not a problem with
> >>> installation or version. The problem is the setting for "LANG": It has
> >>> to be LANG=en_US.UTF-8 and not LANG=de_DE_EURO which is the standard
> >>> for german!
> >>></quote>
> >>>
> >>> Surely (base) perl modules aren't dependent on language?
> >>
> >> They shouldn't be. It might be a bug in perl, in the module or in a
> >> system library. Or it might be a bug in your script. It is impossible to
> >> tell with the information you have given.
> >
> > Considering the statement from 'the user', this must be something which
> > causes the behaviour of some perl code to change because it is using a
> > German locale. Considering what is in a locale definition, this makes
> > LC_NUMERIC the most likely candidate, especially considering that this
> > is the only locale-information used as part of version checking (by
> > Perl_upg_version in util.c).
>
> Yes, I know. But I couldn't reproduce it. And that's not very
> surprising: Many people use perl with a German locale, so it can't be
> something generic like "perl doesn't work with a German locale" or "use
> feature doesn't work with a German locale". It has to be something more
> specific, like a bug in the locale implementation of the user's system
> (but Dave hasn't told us what system it is) or the way a certain feature
> is used (but Dave hasn't told us anything about his script). But it is
> impossible to find out what it is unless Dave volunteers more
> information.
A little difficult to post extra info from the user as I only have a
jpeg of the errors rather than something I can cut and paste :-(
The script starts:
use strict;
use warnings;
use Carp:
use Encode;
Compilation failed in require at .... line 3 - ie the "use Carp" line.
System is OS/2 his perl is 5.10.0. (Yes I know :-) )
If you follow the links from the posted forum you end up with a C test
program. I have built that on my system but as I am in the UK my
system is defaulting to using a 'point' anyway. I have yet to persuade
it to start up in a different locale. I know how to get a program to
use a different language but that does not seem to help. I have posted
this problem to an OS/2 tech group in the hope they may throw some
light on the problem - assuming it is a similar one in that
setlocale() is not working correctly as per the forum post.
--
Regards
Dave Saville
------------------------------
Date: Mon, 23 Dec 2013 23:07:32 +0200
From: George Mpouras <gravitalsun@hotmail.foo>
Subject: Re: tricky stdout
Message-Id: <l9a8mq$2ck3$1@news.ntua.gr>
Στις 23/12/2013 17:47, ο/η Jürgen Exner έγραψε:
> "How can I open a pipe both to and from a command?"
use IPC::Open2 is doing the trick , thanks
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V11 Issue 4100
***************************************
