[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/5] maint: ensure that MB_CUR_MAX is defined even when !MBS_
|
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:32:34 -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 08:26, Paolo Bonzini wrote:
> Exactly my point, mbrlen could return a value > 1, while MB_CUR_MAX could
> have been #undef'ed and redefined to 1.
Ah, sorry, I guess I misunderstand the issue.
Why don't we use "#define MB_CUR_MAX MB_LEN_MAX"
as a fallback then, instead of "#define MB_CUR_MAX 1"?