The bottom line is that 0xa0 is part of \h in ASCII, but 0x41 is not so in EBCDIC. Is that a built in definition, or does PCRE make the determination? /\h/SI Capturing subpattern count = 0 No options No first char No need char Subject length lower bound = 1 Starting chars: \x09 \x20 \xa0 . . . . . . . . . . . . . . Menu Utilities Compilers Help ───────────────────────────────────────── BROWSE ZATLAS1.PCRE.SYSOUT(TSTOT14) Command ===> /\h/SI Capturing subpattern count = 0 No options No first char No need char Subject length lower bound = 1 Starting chars: \x05 \x40 Ze'ev Atlas -- ## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
- Re: [pcre-dev] issues with EBCDIC and pcretest ph10
- Re: [pcre-dev] issues with EBCDIC and pcretest ph10
- Re: [pcre-dev] issues with EBCDIC and pcretest Ze'ev Atlas
- Re: [pcre-dev] issues with EBCDIC and pcretest Ze'ev Atlas
- Re: [pcre-dev] issues with EBCDIC and pcretest Ze'ev Atlas
- Re: [pcre-dev] issues with EBCDIC and pcretest ph10
- Re: [pcre-dev] issues with EBCDIC and pcretest Ze'ev Atlas
- Re: [pcre-dev] issues with EBCDIC and pcretest Ze'ev Atlas
- Re: [pcre-dev] issues with EBCDIC and pcretest ph10
- Re: [pcre-dev] issues with EBCDIC and pcretest Ze'ev Atlas
- Re: [pcre-dev] issues with EBCDIC and pcretest Ze'ev Atlas
- Re: [pcre-dev] issues with EBCDIC and pcretest ph10
