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: Fri, 24 Feb 2023 08:34:03 -0800 Organization: A noiseless patient Spider Lines: 56 Message-ID: <86bkljaupw.fsf@linuxsc.com> References: <86ilgdcwis.fsf@linuxsc.com> <86sfexbwps.fsf@linuxsc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader01.eternal-september.org; posting-host="3119ccfe80da58d8ce67bcaefec134df"; logging-data="2384418"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19SA4sWpxa4N7AZym6bpcw1T/NFBC445RA=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:V0J+so31WIsYMxrhRI0zX0nKLMo= sha1:y8DoITqBJBxkrQhNP2QGloHxNmY= Xref: csiph.com comp.lang.c++:89289 scott@slp53.sl.home (Scott Lurndal) writes: > Tim Rentsch writes: > >> 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. > > const char *source_pointer = source; > char *dest_pointer = dest; > > while (*source != '\0') *dest_pointer++ = *source_pointer++; > > I would call that moving the data, not processing the data. I think it's fair to say that any effort that involves activity by the processor may be called processing. Furthermore your earlier message says "displays". The code shown doesn't do any displaying.