Also, there are some things that break in Java programs when there are
presuppositions on the character set being ASCII, and it turns out to be EBCDIC.
One goal could be to support Unicode the way Java does; another goal could be to
go beyond Java and solve the latter case: that would be truly a solution in the
spirit of the Rexx language.
Given that the NetRexx compiler runs on EBCDIC machines from binaries, I think
the Java folk really did a pretty good piece of design (and in 199x). However
it is always possible to write programs that are presuppose ASCII or EBCDIC (for
example, uppercasing by changing a specific bit in a character encoding).
Languages won't solve that except by prohibiting meddling with the bits of a
character (perhaps the right thing to do -- but then the language is no longer
'general purpose'?).
In the case of NetRexx that's all rather academic at the moment; it is dead
until RexxLA takes it over. Any progress on that?
Mike
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
