Hi Philip
Could you please guide me to where in the code you handle \c, so I could code
either handling it under EBCDIC or issue an eror that it is not supported.
Thanks
Zeev Atlas
Sent from Yahoo Mail on Android
From:p...@hermes.cam.ac.uk p...@hermes.cam.ac.uk
Date:Wed, Jun 10, 2015 at
https://bugs.exim.org/show_bug.cgi?id=1642
Bug ID: 1642
Summary: Tests fail due to stack space being limited to 16 M
Product: PCRE
Version: 10.10 (PCRE2)
Hardware: x86
OS: Linux
Status: NEW
Severity: bug
https://bugs.exim.org/show_bug.cgi?id=1642
Zoltan Herczeg hzmes...@freemail.hu changed:
What|Removed |Added
CC||hzmes...@freemail.hu
---
In my opinion, for the \c sequences, pcre_internal.h should have a section to
explicitly define the below characters (taken from perlebcdic). Something like:
#if defined NATIVE_ZOS #if defined IBM1047#define CHAR_SOH \x01..#define
CHAR_DEL \x07.#elseif defined IBM037..#endif/* ASCII
Good morning,
Thank you for the information! I fully understand this is all voluntary, and
we greatly appreciate the assistance given so far. We’ll be on the lookout for
a new update :)
Have a great week!
—
Jacob Perkins
Product Owner
cPanel Inc.
jacob.perk...@cpanel.net
