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: Thu, 17 Oct 2019 05:43:14 -0700
Organization: A noiseless patient Spider
Lines: 28
Message-ID: <86y2xj4k65.fsf@linuxsc.com>
References: <STKlF.8551$oU2.5908@fx21.iad> <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> <20191014013916.333bfd71e8363156058a1b2e@gmail.com> <86imor73wp.fsf@linuxsc.com> <20191015002630.213bbd842f2f5aa17c73015d@gmail.com> <8636fs6adz.fsf@linuxsc.com> <20191016181735.50831f7a43e770182ac09123@g{oogle}mail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="f160be45e7b63fa8f4ae90cda1d207ba"; logging-data="1846"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18b27lgYtDpbW9QQA1AShIyTc+HUY3TFA8="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:vyZcJjBhqWCgFFlFzJUeNrthIJ4= sha1:qf7bScAzLw/ibnn+C9BnVx5skMU=
Xref: csiph.com comp.lang.c:147015

Anton Shepelev <anton.txt@g{oogle}mail.com> writes:

> Tim Rentsch to Anton Shepelev:
>
>>> I found the C preprocessor so hard that I failed to write
>>> even a simple macro for the generation of function names
>>> with a custom prefix, e.g. MY_Func1, MY_Func2 vs.
>>> HIS_Func1 and HIS_Func2, where MY and HIS may be
>>> #define'd.  I became stuck at macro concatenation and
>>> stringizing via # and ##.  Maybe I should have tried
>>> harder.
>>
>> The C preprocessor is tricky.
>
> Thank you for the post, Tim.  This is a quick note that I
> have actually made it, as I wrote earler:
>
>> I grew ashemed and wrote this yestertday.
>
> I meant I had written a solution to my problem.  GCC online
> documentaiton turned out quite useful in the part about the
> preprocessor.

Ahh I see.  Excellent.

Since you have now learned how to solve the problem, and have
actually written a solution, do you have any comments or
feedback for me on my explanations?