[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gawk mbstate_t problem on hppa2.0w-hp-hpux11.11
From: |
Michael Elizabeth Chastain |
Subject: |
Re: gawk mbstate_t problem on hppa2.0w-hp-hpux11.11 |
Date: |
Mon, 15 Dec 2003 12:43:06 -0500 (EST) |
> My interpretation of this page is that mbstate_t is mandatory.
> The ``[Option Start]'' tag is in the middle of paragraph, suggesting
> that only the second sentence, speaking about ``more than 2 levels'' is
> an XSI extension.
However, the [CX] tag applies to the whole section.
> But even if my interpretation were wrong, and mbstate_t were optional,
> I'd still call the situation ``broken'' though it would be conforming
> to the broken standard.
We'll probably just have to disagree on the theoretical level here.
mec> readline already implements proposal (B), but it has a glitch in the
mec> implementation.
stepan> It must be tricky and I wouldn't wish to struggle with this.
And after two minutes of actually reading readline code, I found some
places where it processes multiple strings simultaneously with
different mbstate_t objects for each string. So readline's fake
mbstate_t's won't work either.
Michael C