diff options
author | Karl Williamson <khw@cpan.org> | 2017-05-30 21:19:20 -0600 |
---|---|---|
committer | Karl Williamson <khw@cpan.org> | 2017-06-01 07:05:16 -0600 |
commit | 53fdf12aede2fd58b0c5ee236a58025184f49def (patch) | |
tree | 2d0278fcf9f332e3da1c1af17a6e64763220c9a2 /embed.h | |
parent | d30277c7df69b4aca40edeb2ae3bf9bb529b01e8 (diff) | |
download | perl-53fdf12aede2fd58b0c5ee236a58025184f49def.tar.gz |
Relax fatal circumstances of unescaped '{'
After the 5.26.0 code freeze, it came out that an application that many
others depend on, GNU Autoconf, has an unescaped '{' in it. Commit
7335cb814c19345052a23bc4462c701ce734e6c5 created a kludge that was
minimal, and designed to get just that one application to work.
I originally proposed a less kludgy patch that was applicable across a
larger set of applications. The proposed patch didn't fatalize uses
of unesacped '{' where we don't anticipate using it for something other
than its literal self. That approach worked for Autoconf, but also far
more instances, but was more complicated, and was rejected as being too
risky during code freeze.
Now this commit implements my original suggestion. I am putting it in
now, to let it soak in blead, in case something else surfaces besides
Autoconf, that we need to work around. By having experience with the
patch live, we can be more confident about using it, if necessary, in a
dot release.
Diffstat (limited to 'embed.h')
-rw-r--r-- | embed.h | 1 |
1 files changed, 1 insertions, 0 deletions
@@ -1042,6 +1042,7 @@ #define is_ssc_worth_it S_is_ssc_worth_it #define join_exact(a,b,c,d,e,f,g) S_join_exact(aTHX_ a,b,c,d,e,f,g) #define make_trie(a,b,c,d,e,f,g,h) S_make_trie(aTHX_ a,b,c,d,e,f,g,h) +#define new_regcurly S_new_regcurly #define nextchar(a) S_nextchar(aTHX_ a) #define output_or_return_posix_warnings(a,b,c) S_output_or_return_posix_warnings(aTHX_ a,b,c) #define parse_lparen_question_flags(a) S_parse_lparen_question_flags(aTHX_ a) |