[397] in java-interest
Some minor items
daemon@ATHENA.MIT.EDU (Douglas Barnes)
Mon Jun 19 20:07:53 1995
Date: Mon, 19 Jun 1995 16:52:06 -0800
To: java-interest@java.sun.com
From: cman@communities.com (Douglas Barnes)
1) "Possible loss of precision" warning. The following code
generates three such warnings:
static byte DIGEST_INFO_PREFIX[] = { 0x30, 0x20, 0x30, 0x0c, 0x06,
0x08, 0x2a, 0x86, 0x48, 0x86,
0xf7, 0x0d, 0x02, 0x05, 0x05,
0x00, 0x04, 0x10 };
This is not because it really loses any bits, but because
there is not an "unsigned byte" type in Java, and the compiler is
concerned that, say 0xf7, is now -9 instead of +247.
2) Array constants. One can initialize arrays from constants (see
above) but can't use array constants in any other context w/o
getting flamed by the compiler. Is there a reason for this? It
would be kind of handy, although one can always throw some
gratuitous {}s around.
3) Low-level support for copying part of one array to another
would be nice. (i.e. something that could safely, but efficiently
give one the semantics of memcpy.)
4) Support for variable #s of arguments. This would have to be
carefully thought out to avoid security problems, but it seems
like it's not completely out of the question. Of course, if
one could easily pass array constants one could fake it.
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
