On Wed, 14 Jun 2017 09:30:39 -0500, John McKown wrote: > >I would like a way to specify that either specific integer variables be in >"Little-Endian" format instead of the IBM z's "Big Endian". It seems to me >that this should be "simple" by just using the "Load Reverse" and "Store >Revere" instructions instead of the normal "Load" and "Store" instructions. >There are 2, 4, & 8 byte variants of these instructions. > Sounds like a new data type [modifier] with automatic or explicit coercions. Coercing functions could be set to no-op, contioned on the platform endianness.
>In addition to the above, I am wondering about the >reading/writing/processing of character data in ASCII instead of EBCDIC. I >know of the ASCII compile option (which I can't review right now due the >the abominable KC being unavailable right now - I am really PISSED at IBM >for this unreliability). Well, enough on that digression. Does the ASCII >compile option allow for reading, writing, and processing of ASCII char > The I/O is handled by autoconversion by the kernel, provided you tag your files and draw the needed pentagrams on your cell wall. >data? Of course, that I'd really like is a "simple" (not iconv) way to >intermix ASCII & EBCDIC characters.> > Need to supply compiler option; XPLINK; and draw more pentagrams in environment variables. Then things such as sprintf() work surprisingly well with all ASCII arguments. Can't then mix with EBCDIC, AFAIK. Sockets is documented as supported; I haven't tried. Environment variables work surprisingly well. Documented lbrary deficiencies: Curses, X11, ... > ... And, yes, I know that I'm opening up a >whole can of mega-worms with this "easy desire". -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
