[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 10 Mar 2024 23:29:40 +0000 (UTC)
From: Thorsten Glaser <tg@...bsd.de>
To: musl@...ts.openwall.com
Subject: Re: [PATCH] complex: fix comment in cacosh
Rich Felker dixit:
>I'm fine with taking this patch as-is, but it naturally raises a
>question: should it instead be:
>
>-/* acosh(z) = i acos(z) */
>+/* acosh(z) = ±i acos(z) */
Yes, please.
>Really the only consideration for not doing this would be if it
>actively breaks compiling in some environments, but I don't think
>that's the case.
I’ve been using UTF-8 in comments in mksh for a while, and it
hasn’t broken on Minix, Plan 9, DEC ULTRIX, 4.4BSD on Windows,
Dell UNIX (bare SVR4), Haiku, Syllable OS, and a plethora of
other old, weird, and other systems. Even Xenix works… and an
EBCDIC system as well.
They just interpret it as pertaining to whatever the local
codepage is, and the EBCDIC system converted it as-if-it-were
“extended ASCII”, but it hasn’t broken anything.
IOW, I haven’t seen a nōn-8bit-clean C compiler yet. Nor sh.
bye,
//mirabilos
--
„Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund,
mksh auf jedem System zu installieren.“
-- XTaran auf der OpenRheinRuhr, ganz begeistert
(EN: “[…]uhr.gz is a reason to install mksh on every system.”)
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.
