RE: [MI400] base64 encoder/decoder for EBCDIC systems

[Jim Langston <jlangston@xxxxxxxxxxx>]

Yes, there is a lot of C specific code in that equation.  I can tell you
what that specific code is doing if you want.

return(((cc >= 33) && (cc <= 60)) || ((cc >= 62) && (cc <= 126))) AND ...
Basically, that is looking for any "standard" type character.  ASCII

Basically, that is taking any character between ASCII 33 through 126 with
the exception of 61 which is equals.  Equals is a special character in
Base64.  Anything 32 and lower are control characters and not part of the
standard displayable alphabet.

if ((dd == '\n') || (dd == '\r') || (dd == '\0')) {;)

\n is newline, carriage return.  \r is return.  \0 is NULL.  Looking for end
of line, terminated either by Carriage Return, Line Feed, or as a NULL
terminated string.

That code should be convertible to EBCDIC as long as you have an EBCDIC
table to look at.

Any more C specific questions you have I will answer if I know (or make up
an answer if I don't <g> j/k ).

You can e-mail me either through this list or directly to me at
jlangston@celsinc.com

Regards,

Jim Langston

-----Original Message-----
From: shahar mor [mailto:shahar_mor@yahoo.com]

 Hi,
Thanks for the reply, i knew you that base 64 had no problem with EBDIC (at
least this :)), only the c source contanis many questions that are ascii
dependent (something like  return(((cc >= 33) && (cc <= 60)) || ((cc >= 62)
&& (cc <= 126))) AND  something like this if ((dd == '\n') || (dd == '\r')
|| (dd == '\0')) {;) so we need to prot it carefully this is doable however
i tried to make it shorter.
Thanks again for your reply