On Wed, Jan 14, 2015 at 7:15 AM, Shane Ginnane <[email protected]> wrote:
> On Wed, 14 Jan 2015 07:01:02 -0600, John McKown wrote:
>
> >SIMD, to me, means instructions akin to the old vector facility on a few
> >of the previous machines.
>
> Think MMX and SSE for your x86 boxes. They've had it since before the turn
> of the century. Not to mention SMT.
> All this is old news to the rest of the computing word.
> Then there is the EBCDIC issue you mentioned - and {big,little}-endian
> concerns of course.
>
I basically ignored the "endian" problem because _my_ C code generally
uses the C "hton..." and "ntoh..." functions to convert my binary number
from/to external format (which I keep in "network order") in files. But
that is just me. Too bad the C compiler does not have a way in the language
itself to say "this is a ??? bit number in host order" and "this is a ???
bit number in network order". But the ugly EBCDIC is just ugly. I rather
like the fact that Java uses Unicode internally for all "character" data
and does the code translation on read/write.
>
> I hope it builds the z base, but I can't see it converting many over.
>
> Shane ...
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>
--
While a transcendent vocabulary is laudable, one must be eternally careful
so that the calculated objective of communication does not become ensconced
in obscurity. In other words, eschew obfuscation.
111,111,111 x 111,111,111 = 12,345,678,987,654,321
Maranatha! <><
John McKown
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
