Paul Marquess <[EMAIL PROTECTED]> writes:
>Good catch Nick.
>
>Instead of completely backing out the "defined $str or return" change, if
>you change it to
>
> unless (defined $str) {
> warnif('uninitialized', 'Use of Uninitialized value in encode_utf8');
> return;
> }
>
>that gives us
My fever is down at last when I released Encode-1.66, available as
follows;
Whole:
http://www.dan.co.jp/~dankogai/Encode-1.66.tar.gz or CPAN
Diff against current: 264 lines
http://www.dan.co.jp/~dankogai/current-1.66.diff.gz
And Changes.
$Revision: 1.66 $ $Date: 2002/05/01 05:4
From: Dan Kogai [mailto:[EMAIL PROTECTED]]
> On Wednesday, May 1, 2002, at 02:10 , Nick Ing-Simmons wrote:
> > Dan Kogai <[EMAIL PROTECTED]> writes:
> >
> > Please don't.
> >
> > $a =~ tr/A/a/;
> >
> > gives a warning so should encode/decode.
>
> How can I be so dumb for not anticipating you say
On Wednesday, May 1, 2002, at 02:15 , Nick Ing-Simmons wrote:
>> $Revision: 1.65 $ $Date: 2002/04/30 16:13:37 $
>> ! Encode.pm
>> encode(undef) no longer warns for C> subroutine entry>. Suggested by Paul.
>
> Can I get warnings + fallbacks yet?
Er, which one are you talking about? Hold on.
On Wednesday, May 1, 2002, at 02:10 , Nick Ing-Simmons wrote:
> Dan Kogai <[EMAIL PROTECTED]> writes:
>
> Please don't.
>
> $a =~ tr/A/a/;
>
> gives a warning so should encode/decode.
How can I be so dumb for not anticipating you say that! (Blame it on the
fever). Paul, I now think Nick's got
Dan Kogai <[EMAIL PROTECTED]> writes:
>
>$Revision: 1.65 $ $Date: 2002/04/30 16:13:37 $
>! Encode.pm
> encode(undef) no longer warns for C subroutine entry>. Suggested by Paul.
Can I get warnings + fallbacks yet?
Can we have a bit to enable warns on undef please ;-)
There are casting issue
Dan Kogai <[EMAIL PROTECTED]> writes:
>On Tuesday, April 30, 2002, at 11:42 , Paul Marquess wrote:
>> I agree that passing undef() to one of the encoding functions may be an
>> edge
>> condition too far, but passing a variable that contains undef is more
>> common.
>>
>> $ perl5.7.3 -w -MEncode -
Paul Marquess <[EMAIL PROTECTED]> writes:
>
>I agree that passing undef() to one of the encoding functions may be an edge
>condition toois more
>common.
nick@bactrian 1078$ perl -w -e "print undef"
Use of uninitialized value in print at -e line 1.
nick@bactrian 1079$ perl -w -e "print $a"
Use
On Wed, May 01, 2002 at 01:42:17AM +0900, Dan Kogai wrote:
> I am wondering if Perl 5.8.0 will be integrated to FreeBSD 5 when I
> released Encode-1.65. FYI FreeBSD 5 release schedule is delayed a whole
> year from November 2001 to November 2002. We would definitely have Perl
> 5.8.0 with no
Paul Marquess <[EMAIL PROTECTED]> writes:
>This is with Encode 1.64
>
>$ perl5.7.3 -w -MEncode -e 'Encode::encode_utf8(undef)'
>Use of uninitialized value in subroutine entry at
>/tmp/bleed/lib/perl5/5.7.3/sun4-solaris/Encode.pm line 183.
>
>I don't know Encode well enough to check if there are an
I am wondering if Perl 5.8.0 will be integrated to FreeBSD 5 when I
released Encode-1.65. FYI FreeBSD 5 release schedule is delayed a whole
year from November 2001 to November 2002. We would definitely have Perl
5.8.0 with no trailing RC (right, Borg?)
Whole:
http://www.dan.co.jp/~da
From: Dan Kogai [mailto:[EMAIL PROTECTED]]
> On Tuesday, April 30, 2002, at 11:42 , Paul Marquess wrote:
> > I agree that passing undef() to one of the encoding functions may be an
> > edge
> > condition too far, but passing a variable that contains undef is more
> > common.
> >
> > $ perl5.7.3 -
World Wide Web
W3C Working Draft 30 April 2002
http://www.w3.org/TR/2002/WD-charmod-20020430
The document's abstract says:
This Architectural Specification provides authors of specifications,
software developers, and content developers with a common reference
for interoperable
On Tuesday, April 30, 2002, at 11:42 , Paul Marquess wrote:
> I agree that passing undef() to one of the encoding functions may be an
> edge
> condition too far, but passing a variable that contains undef is more
> common.
>
> $ perl5.7.3 -w -MEncode -e 'Encode::encode_utf8($a)'
> Name "main::a"
From: Dan Kogai [mailto:[EMAIL PROTECTED]]
> On Tuesday, April 30, 2002, at 07:14 , Paul Marquess wrote:
> > This is with Encode 1.64
> >
> > $ perl5.7.3 -w -MEncode -e 'Encode::encode_utf8(undef)'
> > Use of uninitialized value in subroutine entry at
> > /tmp/bleed/lib/perl5/5.7.3/sun4-solaris/E
On Tuesday, April 30, 2002, at 07:14 , Paul Marquess wrote:
> This is with Encode 1.64
>
> $ perl5.7.3 -w -MEncode -e 'Encode::encode_utf8(undef)'
> Use of uninitialized value in subroutine entry at
> /tmp/bleed/lib/perl5/5.7.3/sun4-solaris/Encode.pm line 183.
>
> I don't know Encode well enough t
At Tue, 30 Apr 2002 09:45:30 -0400,
Thurn, Martin (Intranet) <[EMAIL PROTECTED]> wrote:
> > > preferred MIME again). How about porting this module into Encode,
> > > which might be useful? ^^^
>
> What exactly do you have in mind?
> Add the charset names used by Encode?
At Tue, 30 Apr 2002 21:29:55 +0900,
Tatsuhiko Miyagawa wrote:
> Well, this module uses I18N::Charset internally to translate encoding
> names into IANA registerd name (and its own table to convert it to
> preferred MIME again). How about porting this module into Encode,
> which might be useful?
Hi,
I've made a tiny PerlFixupHandler to guess files' encodings and
automatically add charset attribute into Content-Type accorging to the
guess, using Encode::Guess and I18N::Charset.
This module can be a powerfull replacement/suppliment for Apache's
Add*Charset stuff. The module can be downloa
This is with Encode 1.64
$ perl5.7.3 -w -MEncode -e 'Encode::encode_utf8(undef)'
Use of uninitialized value in subroutine entry at
/tmp/bleed/lib/perl5/5.7.3/sun4-solaris/Encode.pm line 183.
I don't know Encode well enough to check if there are any other places this
will strike.
Paul
Folks,
I gotta go in 5 minutes so I just dump the README file after the sig.
Dan the Encode Maintainer
NAME
Encode::JIS2K - JIS X 0212 (aka JIS 2000) Encodings
INSTALLATION
To install this module type the following:
perl Makefile.PL
make
make test
make install
On Monday, April 29, 2002, at 07:38 , SADAHIRO Tomoyuki wrote:
> I doubt whether users of 'euc-jp' will
> assume it to be a combination with JIS X 0213.
They don't have to because 'euc-jp' behaves exactly the same as before
so long as the charset is in ASCII/JISX(0201|0208|0212).
> Such a mixin
22 matches
Mail list logo
