Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: Sort char array
Date: Sat, 12 Oct 2019 23:06:50 -0700
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <86zhi56ux1.fsf@linuxsc.com>
References: <STKlF.8551$oU2.5908@fx21.iad> <qnknn7$hs7$1@dont-email.me> <dd99aeb0-e773-4bf8-8244-3b2564f992c1@googlegroups.com> <qnl92t$ns$1@dont-email.me> <afd25eab-3bfd-4746-a732-16bc57ba66a6@googlegroups.com> <87tv8ggaxh.fsf@bsb.me.uk> <ysEnF.1045432$WI2.659809@fx34.am4> <87mue8fx7b.fsf@bsb.me.uk> <1QInF.797536$aq7.506537@fx09.am4> <875zkwf27e.fsf@bsb.me.uk> <FqZnF.2707959$dw4.1762701@fx12.am4> <87a7a66eyk.fsf@bsb.me.uk> <tt8oF.2726927$dw4.1608272@fx12.am4> <qns9a4$rmq$1@dont-email.me> <6%ioF.849405$893.123190@fx02.am4> <qnsipf$h1a$1@dont-email.me> <VqloF.2765410$dw4.2477092@fx12.am4> <qnt1ju$90l$1@dont-email.me> <YAooF.296775$3C5.108226@fx01.am4> <t_toF.117829$LG2.38599@fx48.iad> <WjuoF.1059364$WI2.610641@fx34.am4>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="6d8ba740c641a3104d644acea37438f0"; logging-data="8217"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1973aZs5vDbMcBUHecEZ8mGKKz/QjznafI="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:NI31TndSI4aQ1xwe9Dymgh8xfFI= sha1:xCVy9O3v3+BSZEpOdu+6h4GHGeM=
Xref: csiph.com comp.lang.c:146911

Bart <bc@freeuk.com> writes:

> On 13/10/2019 01:13, Richard Damon wrote:
>
> [how to find the maximum value of a typedef'ed type name]
>
>> You also should be able to build something
>> like that out of C's newish _Generic support
>
> _Generic has a problem, because you can't for example have both
> int64_t and long long int as cases, if they are the same type, as they
> will clash.  This can happen when int64_t is defined in terms of long
> long int.
>
> Even if not the same type, it can fail on a machine where they are.

Think harder.  This isn't that hard a problem.

An important thing to understand about Bart is he isn't looking
for answers, he's looking for an argument.  He isn't trying to
solve problems;  if a solution is suggested it will elicit from
him either (a) some disagreement or complaint about the solution,
or (b) a change of subject to another "problem".  Wash, rinse,
repeat.  In essence there is really only one problem:  Bart is a
narcissist, and the only ideas that have value are the ones he
likes (or even better, that he thought up himself).  This problem
will never be resolved by any technical discussion.