[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2533200.g9kxISXj3W@omega>
Date: Sun, 20 Sep 2020 21:21:48 +0200
From: Bruno Haible <bruno@...sp.org>
To: Rich Felker <dalias@...c.org>
Cc: "Dmitry V. Levin" <ldv@...linux.org>, config-patches@....org, musl@...ts.openwall.com
Subject: Re: Re: OS detection wrong on Alpine Linux 3.10
Rich,
POSIX — like many other standard — allows different implementations to
behave differently. For example, iconv_open() and setlocale() behave
differently in different POSIX-compliant libc implementations. This is
OK. There is nothing wrong with it on either side.
Unit tests [1] need to take into account the actual behaviour of the
software. It is normal that a unit test's core function produces a
different result with musl than with glibc. The "expected outcome"
part of the unit test, in this case, needs to be different. This is
an actual, practical need to know whether the config triple ends in
linux-gnu vs. linux-musl.
> There is one kinda legitimate purpose for detecting specifically musl:
It is not your role to tell us which code we write is "legitimate" and
which code is not. I am a grown-up programmer.
Bruno
[1] https://en.wikipedia.org/wiki/Unit_testing
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
