In <[EMAIL PROTECTED]>, on 07/02/2006
at 01:39 PM, Steve Comstock <[EMAIL PROTECTED]> said:
>I'd like to see z/OS last for another 5-7 years and the to be
>replaced with something I call U/OS - for Unicode/OS.
For that to be viable a lot of work would need to be put into the
transition and into inter-operability with existing systems. That
means that you would need to compromise on some things.
>* 64-bit only, from the ground up; no line; no bar
What do you do about legacy applications?
>* Character data normally encoded in UTF-16! This would
> take no new hardware instructions. Abolish EBCDIC, but
> do not replace it with ASCII but rather with UTF-16.
> No more codepage issues, except for a set of utility
> programs to convert existing files and databases to
> UTF-16
You would still have code page issues due to communication with the
outside world.
>* One of the major problems is Unicode input,
Why is that a problem? There's UTF-8 support in, e.g., Linux, OS/2.
One thing missing from the list would be for all files to be memory
mapped.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
