Craig A. Berry <[EMAIL PROTECTED]> writes:
>FWIW, I made a smaller reproducer:
>
>$ create vms_problem.t
>use strict;
>use FileHandle;
>use Encode (":all");
>{
> no warnings;
>}
>
>open my $fh, '<:encoding(euc-kr)', 'ksc5601.enc' or die "ksc5601.enc : $!";
>my $dtext = join('' => <$fh>);
>close $fh;
>^Z
>$ perl vms_problem.t
>euc-kr "\xAD" does not map to Unicode at vms_problem.t line 9, <$fh> line 230.
Good - that decouples the whole thing from previous runs etc. etc.
Why the FileHandle and warnings bits - are they necessary to see the problem?
>
>I guess the next thing is to create a build for the VMS debugger and go
>slogging around in the vicinity of PerlIO_read, though I'm not sure exactly
>what I'm looking for.
We moved on a bit over weekend ...
1. Can you grep CPP'ed perlio.c for "right" VMS hackery for ungetc() ?
2. Can you try using :perlio layer rather than :stdio layer and
see if that helps
on UNIX that would be
PERLIO=perlio perl vms_problem.t
--
Nick Ing-Simmons
http://www.ni-s.u-net.com/
