Bruno Haible writes:
>> I was thinking maybe adding a way to force ASCII on Haiku, but that
>> seems to hacky.
>
> How would you want to do that? If the system has no locale with ASCII
> or ISO-8859-1 encoding (such as on macOS, Haiku, and Android), you can't
> force it.
You're right. That was a
Thanks for catching my portability error. I installed that into 'patch'
master.
At first I was worried that the patch relied on Haiku errno values not
being -1, since the Gnulib documentation said only that they can be
negative. However, I discovered that Haiku errno values are all close to
I
Collin Funk wrote:
> test failures in Coreutils, for example, due to the following lines in
> localcharset.c:
>
> See the following lines:
>
> /* On Mac OS X, all modern locales use the UTF-8 encoding.
>BeOS and Haiku have a single locale, and it has UTF-8 encoding. */
> # if
Hi Bruno,
Bruno Haible via Gnulib discussion list writes:
> Some portability problems are specific to Haiku. Therefore it makes sense
> to mark some test failures as "expected failure on Haiku only".
Makes sense, thanks.
Somewhat related, I recently tried Haiku for the first time and noticed
t
Some portability problems are specific to Haiku. Therefore it makes sense
to mark some test failures as "expected failure on Haiku only".
2025-02-05 Bruno Haible
test-xfail: Define a condition for Haiku.
* modules/test-xfail (configure.ac): Define OS_IS_HAIKU conditional.
dif
The module 'string-buffer' supports creating a string piece by piece,
from the start to the end.
But in some cases, one needs to create a string piecemeal, from the end
to the start. Same thing, just in the opposite direction.
The C++ library authors would extend the 'string-buffer' type to allow
On 2025-02-04 13:38, Bruno Haible wrote:
Paul Eggert wrote:
For situations like these I prefer "default: unreachable ();" to
"default: abort ();", as "unreachable ()" lets the builder decide
whether to abort or optimize; but it's no big deal.
If there's only the slightest chance of that 'defau
