Marc, I've just looked at the C99 draft standard (I don't feel like buying a copy of C89 right now, so please correct me if they differ here).
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n869/ Section 7.20.8.1.4, specifies that the null termination is indeed optional. While I agree that it probably would have been wise of the OpenBSD devs to do this, their implimented behavior does still conform to the standard (unless, of course, C89 & C99 differ on this point). So _technically_, the bug does lie in URxvt. ----- Original message ----- From: Marc Lehmann <[email protected]> To: Yarin <[email protected]> Subject: Re: Unicode related bug fix application Date: Tue, 27 Mar 2012 16:05:19 +0200 On Tue, Mar 27, 2012 at 02:12:29AM -0500, Yarin <[email protected]> wrote: > > Hmm, if that were the case, mbstowcs would use more than one wide > > character per input octet - under what conditions would this > > legally happen? > > I don't know whether or not that would conform to specifications. > Only that the author expected it to null terminate the string, > and it doesn't on OpenBSD, which introduces an obvious bug. You mean it never 0-terminates? That's clearly a bug in OpenBSD, and cannot be fixed in urxvt - you should report this bug to the openbsd developers. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / [email protected] -=====/_/_//_/\_,_/ /_/\_\ _______________________________________________ rxvt-unicode mailing list [email protected] http://lists.schmorp.de/cgi-bin/mailman/listinfo/rxvt-unicode
