This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: UTF-16 not supported?

From: Tom Tromey <tromey at redhat dot com>
To: Suresh Raman <sugansha at yahoo dot com>
Cc: java at gcc dot gnu dot org
Date: 16 Aug 2002 11:45:12 -0600
Subject: Re: UTF-16 not supported?
References: <20020815220201.86425.qmail@web10307.mail.yahoo.com><8765ya21e6.fsf@fleche.redhat.com>
Reply-to: tromey at redhat dot com

>>>>> "Tom" == Tom Tromey <tromey@redhat.com> writes:

Tom> I think there are situations where the encoding/decoding
Tom> functions can mistake "lack of progress" for "I'm done".  I'm not
Tom> certain but it is possible that this code triggers that bug.

I did some debugging, and the above is is sort of what is going on.
The problem is that our workaround for a glibc 2.1.3 bug causes us to
fail in a different way when the buffer is too small.

I think it would be better for us to work out a way for this code to
work on systems that don't have the glibc bug, and let glibc 2.1.3
systems continue to fail one way or another.

Tom

References:
- UTF-16 not supported?
  - From: Suresh Raman
- Re: UTF-16 not supported?
  - From: Tom Tromey

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]