This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: WIN-09.: shs.h, shs.cc, natSimpleSHSStream.cc: use uint<n>_t instead of LONG and BYTE
- From: Tom Tromey <tromey at redhat dot com>
- To: Adam Megacz <patches at lists dot megacz dot com>
- Cc: java-patches at gcc dot gnu dot org
- Date: 01 Feb 2002 13:37:54 -0700
- Subject: Re: WIN-09.: shs.h, shs.cc, natSimpleSHSStream.cc: use uint<n>_t instead of LONG and BYTE
- References: <86sn8lmwww.fsf@megacz.com> <86g04lmw9n.fsf@megacz.com>
- Reply-to: tromey at redhat dot com
>>>>> "Adam" == Adam Megacz <patches@lists.megacz.com> writes:
Adam> Is this kosher? uint<n>_t should be more portable than simply
Adam> assuming that a "unsigned int" is 32 bits. Win32 typedef's LONG
Adam> to something obscure anyways.
Can we assume uint<n>_t on all platforms? Or would we need configury
support here?
Adam> -typedef unsigned char BYTE;
Adam> -typedef unsigned int LONG; /* A 32-bit type */
Simpler in our code would be to use jbyte and jint.
We know jint is a 32-bit integer.
However, I don't know if `unsigned jint' will work or not.
Tom