Autrijus Tang <[EMAIL PROTECTED]> writes:
>Daniel Shane wrote:
>> This seems to be a real problem that is showing up every now and then. Seems
>> there are not enough people using PAR and UTF8 yet to place this bug at the
>> top of the priority list :(
>
>No, it's just that I lack the neccessary Perl internal-fu to trace it
>down, too.
>
>I can, however, reduce it to this minimal test case under PAR 0.76_99:
>
> pp -e "use utf8; /\x{100}/i;"
>
>It contains only neccessary elements: "utf8" has to be in scope; the
>character has to be >0xFF; the /i flag has to be there.
>
>The generated executable emits those error messages on ActivePerl
>5.8.2.808 (but should also fail similarily on other platforms):
>
> Use of uninitialized value in pattern match (m//) at
> /loader/0xfc275c/utf8_heavy.pl line 185.
> (several lines of the same error as above)
> panic: swash_fetch at script/ppq5rNh.pl line 1.
>
>Does it ring a bell to anyone? I think it's time to Cc p5p now. :-/
I know roughly how swash stuff works, but not what PAR is.
The 'swash' stuff is used for uc/lc and the like when chars > 0x100
are involved. Snag is perl uses regular expressions to load the
tables - so if 1st use of table is in a regular expression odd things
happen.
What does 'pp' do - can the above be "expanded" into normal perl?
>
>Thanks,
>/Autrijus/
