Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups: comp.lang.c++
Subject: Re: GCC hasn't even gotten around to sequencing argument evaluation
Date: Wed, 06 Apr 2022 15:54:34 -0700
Organization: None to speak of
Lines: 32
Message-ID: <87mtgxomad.fsf@nosuchdomain.example.com>
References: <t28g93$cou$1@dont-email.me> <t298jp$duj$1@dont-email.me> <t29ej1$5dk$1@dont-email.me> <t29mij$1bk8$1@gioia.aioe.org> <t29q1c$hf1$1@dont-email.me> <t29qms$18lf$1@gioia.aioe.org> <t1tg4hdokpjqagckllag4839rkn9ssag4a@4ax.com> <t2e9qb$q6l$1@gioia.aioe.org> <t2efo4$jqc$1@dont-email.me> <t2f03t$kt$1@gioia.aioe.org> <t2f420$q7p$1@dont-email.me> <t2hmk6$1nno$1@gioia.aioe.org> <t2hnnm$c47$1@dont-email.me> <t2hon3$rje$1@gioia.aioe.org> <t2kncv$ite$1@dont-email.me> <t2l10e$1h9d$1@gioia.aioe.org> <87tub5op6s.fsf@nosuchdomain.example.com> <t2l2vi$6qm$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Injection-Info: reader02.eternal-september.org; posting-host="6c9ede39ce33455a77cf7731f598ba3c"; logging-data="14915"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1858rhKLjgnsmxqegAbVmXQ"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux)
Cancel-Lock: sha1:5B+pRuHYBT1n+5lkg7OQKwce7Xk= sha1:5w7FrEZGv2yKfXapIQ/9xk8OVZk=
Xref: csiph.com comp.lang.c++:83512

Sams Lara <samlara622@gmail.com> writes:
> On 06/04/2022 22:51, Keith Thompson wrote:
>>
>> Can you configure your news software to use UTF-8 and/or avoid NO-BREAK
>> SPACE characters?
> OK try this:
>
> string BinaryString(int Number)
> {
>      if (Number == 0)
>      {
>          return "0";
>      }
>      else
[snip]

That looks better in my newsreader.

I'll note that you still have NO-BREAK SPACE characters, but now my
newsreader can figure out how to display.  But if I save the article
to a source file, gcc complains about stray '\240' characters.

You have this in your article headers:
Content-Type: text/plain; charset=windows-1252; format=flowed

I still recommend using UTF-8 and avoiding NO-BREAK SPACE characters,
but I'm not going to worry about it.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips
void Void(void) { Void(); } /* The recursive call of the void */