Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: Sort char array
Date: Fri, 11 Oct 2019 02:26:08 -0700
Organization: None to speak of
Lines: 17
Message-ID: <lna7a7tyz3.fsf@kst-u.example.com>
References: <STKlF.8551$oU2.5908@fx21.iad> <e2c6fd6e-be6b-4320-b4ce-09f574f40fd2@googlegroups.com> <n0EmF.2667134$c8w1.1556251@fx08.am4> <20191007131948.c9f28d44bcd105e7a153069a@g{oogle}mail.com> <2xFmF.867378$yH4.431562@fx18.am4> <qnf974$aiu$1@dont-email.me> <XyHmF.665592$qd4.648019@fx17.am4> <20191007174244.385138503569a8bc6d4eec9d@g{oogle}mail.com> <rvKmF.2513170$dw4.1447457@fx12.am4> <20191008022725.36fbd95aa45ba185290e5e11@gmail.com> <1q_mF.841756$Zy3.585129@fx33.am4> <20191009020207.b533aa1c6d95f44eb314ffc1@gmail.com> <qnkd2j$hpb$1@dont-email.me> <5alnF.1041354$WI2.353384@fx34.am4> <qnknn7$hs7$1@dont-email.me> <dd99aeb0-e773-4bf8-8244-3b2564f992c1@googlegroups.com> <qnl92t$ns$1@dont-email.me> <20191010003208.ff29e87d2de1e17c50f96c74@gmail.com> <qnmqp7$n5p$1@dont-email.me> <ln1rvkv6ob.fsf@kst-u.example.com> <qnpek4$uvo$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="fa3c8307132564ce59634920bb278689"; logging-data="14676"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1//zi8PXZaE3FIZ2iLWTwTy"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:zEOH12oSYcpopI/uBCj3BgCuFfk= sha1:oifcWQfKgsuej226JPxBJi8FdF0=
Xref: csiph.com comp.lang.c:146870

David Brown <david.brown@hesbynett.no> writes:
> On 10/10/2019 19:42, Keith Thompson wrote:
[...]
>> No thanks.  It's bad enough that we already have that problem with,
>> for example, unsigned long and size_t.  And I fail to see what
>> benefit you'd get from treating long and long long as compatible,
>> other than tolerating bad code.
>
> I'm guessing you don't make much use of fixed size types from <stdint.h>.

I'm not sure why you'd guess that.  I try to use them consistently, and
without non-portable assumptions.

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */