The real question is why, but really why, IBM had to introduce this EBCDIC 
horror, where symbols like [,], ^ and some less signifacant ones moved around 
like dry leaves in the fall wind.  Why didn't IBM jist left them in one place.I 
did never find any explanation, let alone logical explanation.  As a maintainer 
of regular expression engine (PCRE) on EBCDIC, I have to deal with the horrible 
results of that stuff on regular basis.  I had to resort to use iconv() not 
between EBCDIC and ASCII, but even within th EBCDIC world.  My users have to 
convert the regex and target strings to some equal base (usually 1047) and back.
Instead of taking responsibility, IBM  just introduced new code pages that 
increased confusion rather than solving the issue.
I am disapointed
ZA

Sent from Yahoo Mail on Android 
 
  On Mon, Feb 13, 2023 at 12:39 PM, Ed Jaffe<edja...@phoenixsoftware.com> 
wrote:   On 2/13/2023 9:27 AM, Charles Mills wrote:
> Any reliance on the visible glyph as an unambiguous indication of the
> underlying bit pattern is going to be fraught.

I know for absolute fact that my 3270 emulators and ISPF are properly 
synchronized to correctly process and display characters using the 
IBM-1047 (Latin 1) code page.

For other characters, I routinely use HEX mode to examine or set them in 
my programs.

Even when using HLASM's helpful, built-in support for EBCDIC->ASCII 
conversion I will undoubtedly examine source listings to be sure all is 
as expected.


-- 
Phoenix Software International
Edward E. Jaffe
831 Parkview Drive North
El Segundo, CA 90245
https://www.phoenixsoftware.com/


--------------------------------------------------------------------------------
This e-mail message, including any attachments, appended messages and the
information contained therein, is for the sole use of the intended
recipient(s). If you are not an intended recipient or have otherwise
received this email message in error, any use, dissemination, distribution,
review, storage or copying of this e-mail message and the information
contained therein is strictly prohibited. If you are not an intended
recipient, please contact the sender by reply e-mail and destroy all copies
of this email message and do not otherwise utilize or retain this email
message or any or all of the information contained therein. Although this
email message and any attachments or appended messages are believed to be
free of any virus or other defect that might affect any computer system into
which it is received and opened, it is the responsibility of the recipient
to ensure that it is virus free and no responsibility is accepted by the
sender for any loss or damage arising in any way from its opening or use.
  

Reply via email to