|
From: | Etienne Gagnon |
Subject: | Re: Classpath build process and VM-specific issues |
Date: | Mon, 05 Apr 2004 20:18:41 -0400 |
User-agent: | Mozilla/5.0 (X11; U; Linux ppc; en-US; rv:1.6) Gecko/20040402 Debian/1.6-4 |
Etienne Gagnon wrote:
FYI: The JNI specification guarantees that jbyte is an 8-bit signed value.
Hmmm... Thinking about all this mess of "non-specified" C byte length... Can JNI actually be implemented on a 16-bit per byte system? Anybody has a reasonable answer? To consider: 5.2.4.2.1 Sizes of integer types <limits.h> [#1] The values given below shall be replaced by constant expressions suitable for use in #if preprocessing directives... ... -- number of bits for smallest object that is not a bit- field (byte) CHAR_BIT 8 ... So, what how would one define "jbyte" on a platform where CHAR_BIT is defined as 16? JNI depends on having such a type. Etienne -- Etienne M. Gagnon, Ph.D. http://www.info.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/
[Prev in Thread] | Current Thread | [Next in Thread] |