|
| From: | Paul Eggert |
| Subject: | Re: [PATCH 1/5] maint: ensure that MB_CUR_MAX is defined even when !MBS_SUPPORT |
| Date: | Mon, 10 Oct 2011 08:21:37 -0700 |
| User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110928 Fedora/3.1.15-1.fc14 Thunderbird/3.1.15 |
On 10/10/11 01:03, Paolo Bonzini wrote: > The reason is that then MB_CUR_MAX would be inconsistent with the > behavior of mbrlen and similar functions. Surely it's OK if MB_CUR_MAX is larger than it strictly needs to be. I can't think of any application that would break if MB_CUR_MAX were set to MB_LEN_MAX on ancient hosts that lacked MB_CUR_MAX.
| [Prev in Thread] | Current Thread | [Next in Thread] |