|
| From: | Paolo Bonzini |
| Subject: | Re: [PATCH 1/5] maint: ensure that MB_CUR_MAX is defined even when !MBS_SUPPORT |
| Date: | Mon, 10 Oct 2011 17:26:10 +0200 |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:6.0.2) Gecko/20110906 Thunderbird/6.0.2 |
On 10/10/2011 05:21 PM, Paul Eggert 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.
Exactly my point, mbrlen could return a value > 1, while MB_CUR_MAX could have been #undef'ed and redefined to 1.
Paolo
| [Prev in Thread] | Current Thread | [Next in Thread] |