develooper Front page | perl.perl5.porters | Postings from March 2003

Re: Encode vs. $ENV{PERL_UNICODE} [Was: Re: Encode trouble]

Thread Previous | Thread Next
From:
Dan Kogai
Date:
March 6, 2003 04:38
Subject:
Re: Encode vs. $ENV{PERL_UNICODE} [Was: Re: Encode trouble]
Message ID:
600A75C3-4FD0-11D7-95A8-000393AE4244@dan.co.jp
On Thursday, Mar 6, 2003, at 21:33 Asia/Tokyo, Dan Kogai wrote:
> I noticed that when I read perlrun again.  But that can still be 
> overcome by  "defined $ENV{PERL_UNICDE}".  However, $ENV{PERL_UNICODE} 
> = 0 has a different meaning again.
>
> Another problem is that the -C switch does NOT change 
> $ENV{PERL_UNICODE} so you can't check the state easily.  Can you make 
> it so that the -C switch changes $ENV{PERL_UNICODE} accordingly?

Oh, no need.  ${^UNICODE} serves the purpose well enough.

(defined ${^UNICODE} and ${^UNICODE} != 0)

should suffice.

Dan the Encode Maintainer


Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About