Matching above-Unicode warning not always output

[p5pRT]

Migrated from rt.perl.org#114148 (status was 'abandoned')

Searchable as RT114148$

[p5pRT]

From @khwilliamson

This is a bug report for perl from khw@​karl.(none),
generated with the help of perlbug 1.39 running under perl 5.17.2.

---

A very few Unicode properties when compiled get optimized into an EXACT
node instead of the typical ANYOF nodes. If such a property is matched
against a string that has above-Unicode code points, the warning message
that is supposed to be emitted isn't.

A way to fix this would be to create a 2nd EXACT node type that did the
check. There probably should be a complete set of EXACTish nodes to
cover all situations.

I don't think it's worth it, at this time anyway, to fix this bug, but
am submitting it so it's documented.

---

---

Flags​:
  category=core
  severity=low

---

Site configuration information for perl 5.17.2​:

Configured by khw at Sun Jul 15 09​:47​:34 MDT 2012.

Summary of my perl5 (revision 5 version 17 subversion 2) configuration​:
  Commit id​: b8a55fe
  Platform​:
  osname=linux, osvers=2.6.35-32-generic-pae,
archname=i686-linux-thread-multi-64int-ld
  uname='linux karl 2.6.35-32-generic-pae #67-ubuntu smp mon mar 5
21​:23​:19 utc 2012 i686 gnulinux '
  config_args='-des -Dprefix=/home/khw/blead -Dusedevel
-D'optimize=-ggdb3' -A'optimize=-ggdb3' -A'optimize=-O0' -Dman1dir=none
-Dman3dir=none -DDEBUGGING -Dcc=g++ -Dusemorebits -Dusethreads'
  hint=recommended, useposix=true, d_sigaction=define
  useithreads=define, usemultiplicity=define
  useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
  use64bitint=define, use64bitall=undef, uselongdouble=define
  usemymalloc=n, bincompat5005=undef
  Compiler​:
  cc='g++', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING
-fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
  optimize='-O0 -ggdb3',
  cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBUGGING
-fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include'
  ccversion='', gccversion='4.4.5', gccosandvers=''
  intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=12345678
  d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
  ivtype='long long', ivsize=8, nvtype='long double', nvsize=12,
Off_t='off_t', lseeksize=8
  alignbytes=4, prototype=define
  Linker and Libraries​:
  ld='g++', ldflags =' -fstack-protector -L/usr/local/lib'
  libpth=/usr/local/lib /lib/../lib /usr/lib/../lib /lib /usr/lib
/usr/lib/i686-linux-gnu
  libs=-lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
  perllibs=-lnsl -ldl -lm -lcrypt -lutil -lpthread -lc
  libc=/lib/../lib/libc.so.6, so=so, useshrplib=false, libperl=libperl.a
  gnulibc_version='2.12'
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E'
  cccdlflags='-fPIC', lddlflags='-shared -ggdb3 -ggdb3 -O0
-L/usr/local/lib -fstack-protector'

Locally applied patches​:

---

@​INC for perl 5.17.2​:

/home/khw/blead/lib/perl5/site_perl/5.17.2/i686-linux-thread-multi-64int-ld
  /home/khw/blead/lib/perl5/site_perl/5.17.2
  /home/khw/blead/lib/perl5/5.17.2/i686-linux-thread-multi-64int-ld
  /home/khw/blead/lib/perl5/5.17.2
  /home/khw/blead/lib/perl5/site_perl
  .

---

Environment for perl 5.17.2​:
  HOME=/home/khw
  LANG=en_US.UTF-8
  LANGUAGE=en_US​:en
  LD_LIBRARY_PATH (unset)
  LOGDIR (unset)

PATH=/home/khw/bin​:/home/khw/print/bin​:/bin​:/usr/local/sbin​:/usr/local/bin​:/usr/sbin​:/usr/bin​:/sbin​:/usr/games​:/home/khw/cxoffice/bin
  PERL5OPT=-w
  PERL_BADLANG (unset)
  SHELL=/bin/ksh

[p5pRT]

From @jkeenan

On Mon, 16 Jul 2012 04​:22​:15 GMT, public@​khwilliamson.com wrote​:

This is a bug report for perl from khw@​karl.(none),
generated with the help of perlbug 1.39 running under perl 5.17.2.

-----------------------------------------------------------------
A very few Unicode properties when compiled get optimized into an
EXACT
node instead of the typical ANYOF nodes. If such a property is
matched
against a string that has above-Unicode code points, the warning
message
that is supposed to be emitted isn't.

A way to fix this would be to create a 2nd EXACT node type that did
the
check. There probably should be a complete set of EXACTish nodes to
cover all situations.

I don't think it's worth it, at this time anyway, to fix this bug, but
am submitting it so it's documented.

Karl, is the value of addressing this bug high enough yet to warrant the effort?

Thank you very much.

--
James E Keenan (jkeenan@​cpan.org)

[p5pRT]

The RT System itself - Status changed from 'new' to 'open'

[p5pRT]

From @khwilliamson

On 12/31/2016 05​:17 PM, James E Keenan via RT wrote​:

On Mon, 16 Jul 2012 04​:22​:15 GMT, public@​khwilliamson.com wrote​:

This is a bug report for perl from khw@​karl.(none),
generated with the help of perlbug 1.39 running under perl 5.17.2.

-----------------------------------------------------------------
A very few Unicode properties when compiled get optimized into an
EXACT
node instead of the typical ANYOF nodes. If such a property is
matched
against a string that has above-Unicode code points, the warning
message
that is supposed to be emitted isn't.

A way to fix this would be to create a 2nd EXACT node type that did
the
check. There probably should be a complete set of EXACTish nodes to
cover all situations.

I don't think it's worth it, at this time anyway, to fix this bug, but
am submitting it so it's documented.

Karl, is the value of addressing this bug high enough yet to warrant the effort?

I don't think so. So what do we do with the ticket? stall it, won't
fix it? I don't know what's best

Thank you very much.

[p5pRT]

From @xsawyerx

On Sat, 31 Dec 2016 20​:48​:56 -0800, public@​khwilliamson.com wrote​:

On 12/31/2016 05​:17 PM, James E Keenan via RT wrote​:

On Mon, 16 Jul 2012 04​:22​:15 GMT, public@​khwilliamson.com wrote​:

This is a bug report for perl from khw@​karl.(none),
generated with the help of perlbug 1.39 running under perl 5.17.2.

-----------------------------------------------------------------
A very few Unicode properties when compiled get optimized into an
EXACT
node instead of the typical ANYOF nodes. If such a property is
matched
against a string that has above-Unicode code points, the warning
message
that is supposed to be emitted isn't.

A way to fix this would be to create a 2nd EXACT node type that did
the
check. There probably should be a complete set of EXACTish nodes to
cover all situations.

I don't think it's worth it, at this time anyway, to fix this bug,
but
am submitting it so it's documented.

Karl, is the value of addressing this bug high enough yet to warrant
the effort?

I don't think so. So what do we do with the ticket? stall it, won't
fix it? I don't know what's best

I think Abandon fits well.

[p5pRT]

From @khwilliamson

Abandoning this ticket as suggested by the pumpking
--
Karl Williamson

[p5pRT]

@khwilliamson - Status changed from 'open' to 'abandoned'