On 16.08.2012 18:22, Corinna Vinschen wrote:
On Aug 16 09:24, Eric Blake wrote:
On 08/16/2012 08:20 AM, Thomas Wolff wrote:
MB_CUR_MAX does not work because its value is 1 at this point
So what about MB_LEN_MAX then? There's no problem using a multiplier,
but a symbolic constant is always be
On Aug 17 10:44, Thomas Wolff wrote:
> On 16.08.2012 18:22, Corinna Vinschen wrote:
> >On Aug 16 09:24, Eric Blake wrote:
> >>On 08/16/2012 08:20 AM, Thomas Wolff wrote:
> >>
> >MB_CUR_MAX does not work because its value is 1 at this point
> So what about MB_LEN_MAX then? There's no proble
On 17.08.2012 11:22, Corinna Vinschen wrote:
...
Anyway, my updated patch (using MB_LEN_MAX) proposes a change here as well.
Thanks. I dropped the hint that 4 is enough. I'm not so sure about
that. Linux, for instance, defines MB_LEN_MAX as 16.
SunOS defines it as 5.
http://www.kernel.org