Path: csiph.com!weretis.net!feeder8.news.weretis.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch
Newsgroups: comp.lang.c++
Subject: Re: Found a use case for `const` by value return, a shared queue
Date: Wed, 22 Feb 2023 06:28:47 -0800
Organization: A noiseless patient Spider
Lines: 39
Message-ID: <86sfexbwps.fsf@linuxsc.com>
References: <86ilgdcwis.fsf@linuxsc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader01.eternal-september.org; posting-host="ac4e296fa9b47119c23b6ef4a9f9b2b8"; logging-data="1626628"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/G96Xm/Gr0Sj09rGRqx7CYPopOEtmlL9I="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:QatUAGViind11Ow0umXpTBmDVdg= sha1:JqzLrT/YCYeTZ0bY9F/BavXTQHc=
Xref: csiph.com comp.lang.c++:89203
scott@slp53.sl.home (Scott Lurndal) writes:
> Tim Rentsch writes:
>
>> "Alf P. Steinbach" writes:
>>
>>> On 2023-02-06 10:35 PM, Scott Lurndal wrote:
>>
>> [...]
>>
>>>> Whatever agent you used to post this wrapped many of the longer lines
>>>
>>> The agent is Mozilla Thunderbird.
>>>
>>> It uses a line continuation scheme that's specified in RFC 3676
>>> section 4.1, of putting a space at the end of a line as continuation
>>> symbol; .
>>>
>>> That's called a "soft line break", and the scheme is called "flowed
>>> format", which you can see in the posting's headers.
>>>
>>> Thus, looking at my posting in TB's usual view it's fine, but the raw
>>> posted text lines are wrapped.
>>
>> Unfortunately some or many of those trailing spaces don't
>> survive getting to the client newsreader in the first place.
>> I've looked carefully. In many cases where the lines are
>> wrapped, the trailing spaces aren't there.
>>
>>> Evidently your newsreader XRN (X news reader) or perhaps your version
>>> of that newsreader, doesn't support RFC 3676's flowed format.
>>
>> I've looked at the raw input, before it ever gets processed by
>> the newsreader. On most of the wrapped lines, no trailing spaces.
>
> XRN doesn't "process" the message, it simply displays it as is.
Surely displaying the message involves some processing,
even if not very much.