This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/28977] UTF-16 endianness differs between gcj and Sun JDK
- From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 7 Sep 2006 18:40:09 -0000
- Subject: [Bug libgcj/28977] UTF-16 endianness differs between gcj and Sun JDK
- References: <bug-28977-13215@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from pinskia at gcc dot gnu dot org 2006-09-07 18:40 -------
(In reply to comment #2)
> Well, I have a library for XML processing that comes with a test suite, and it
> expects the Sun behaviour. Besides it's documented in Sun's API, so it can
> potentially matter.
Really if the testsuite (or the library itself) does not check the BOM, then it
is incorrect. Yes we should follow the Java documention.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28977