This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: bug in mbrtowc?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-talk at cygwin dot com
- Date: Tue, 28 Jul 2009 13:05:38 +0200
- Subject: Re: bug in mbrtowc?
- References: <416096c60907271456x5e8cb3f7y64433d542ec6cdcb@mail.gmail.com> <20090728091413.GJ18621@calimero.vinschen.de> <4A6ED4D6.5080905@gmail.com>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk at cygwin dot com>
On Jul 28 11:37, Dave Korn wrote:
> Corinna Vinschen wrote:
> >
> > That's a bug in the newlib function __utf8_mbtowc. I'm really surprised
> > that this bug has never been reported before since it's in the code for
> > years, probably since it has been introduced in 2002.
>
> I'm not terribly surprised. How much use for i18n is there in the typical
> embedded microcontroller? We're probably the first project to really use this
> code in anger(*);
After having sent my mail I started to wonder as well. Unicode and
wide-char support in a 64K RAM board sounds like waste. I had expected
that RTEMS is using this a bit more, though.
> cf. also how we still shake out the odd longstanding
> floating point bug in newlib, another area that is significantly less-used in
> tiny embedded apps than on desktop workstations.
plus the entirely missing area of long double support.
Corinna