warnings as XS #9

Open
rurban opened this Issue Sep 11, 2015 · 1 comment

Projects

None yet

1 participant

@rurban
Member
rurban commented Sep 11, 2015

Rewrite warnings.pm which is generated as pure XS. esp. to save memory

A regular XS extension, with a stable set of .xs and .h files, and a warnings_xs.PL regen and definition
script (prev. regen/warnings.pl), which updates the keys in place.
required gperf so far, as with Config as XS.

Seperate into a pure read-only perfect hash, and a user-extendable warnings::register hash.
Check against Carp in XS and PP Carp.

See branches feature/CM-367-cperl-warnings-xs-carp and feature/CM-370-cperl-warnings-xs

@rurban rurban added the enhancement label Sep 11, 2015
@rurban rurban self-assigned this Sep 11, 2015
@rurban
Member
rurban commented Sep 11, 2015

Status: One small nasty bug left, in 9enabled

@rurban rurban added a commit that referenced this issue Jan 6, 2016
@rurban rurban Config: fix length test with inc_version_list_init
See [perl11/p5-Config #9].
Broken with a non-empty inc_version_list_init
70282c7
@rurban rurban pushed a commit that referenced this issue Oct 26, 2016
@khwilliamson khwilliamson Add macro for Unicode Corregindum #9 strict
This macro follows Unicode Corrigendum #9 to allow non-character code
points.  These are still discouraged but not completely forbidden.

It's best for code that isn't intended to operate on arbitrary other
code text to use the original definition, but code that does things,
such as source code control, should change to use this definition if it
wants to be Unicode-strict.

Perl can't adopt C9 wholesale, as it might create security holes in
existing applications that rely on Perl keeping non-chars out.
a82be82
@rurban rurban added the in progress label Dec 1, 2016
@rurban rurban added a commit that referenced this issue Jan 3, 2017
@khwilliamson @rurban khwilliamson + rurban Add macro for Unicode Corregindum #9 strict
This macro follows Unicode Corrigendum #9 to allow non-character code
points.  These are still discouraged but not completely forbidden.

It's best for code that isn't intended to operate on arbitrary other
code text to use the original definition, but code that does things,
such as source code control, should change to use this definition if it
wants to be Unicode-strict.

Perl can't adopt C9 wholesale, as it might create security holes in
existing applications that rely on Perl keeping non-chars out.
0168dfb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment