Path: ...!feeds.phibee-telecom.net!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Richard Heathfield Newsgroups: sci.crypt Subject: Re: Sci.Crypt Open Secret Date: Mon, 8 Aug 2022 14:29:20 +0100 Organization: Fix this later Lines: 33 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Mon, 8 Aug 2022 13:29:21 -0000 (UTC) Injection-Info: reader01.eternal-september.org; posting-host="6ef56c5ae7a80a42cbda4d1b27aac29b"; logging-data="1004660"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19sRismvrXUAN4d83EbOLg6CsFZLcRp1VzrCqTFx1K4qQ==" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Cancel-Lock: sha1:7RiSF5U/3/YBn5zQ8FL61kViRVk= In-Reply-To: Content-Language: en-GB Bytes: 2188 On 08/08/2022 1:54 pm, Rich wrote: > One question though, any idea why my gcc complains like this, > unless I convert the final fprintf to a single line string?: Some information for you: 1) In my source code it is a single line string; 2) I encrypted the source without adding any newlines; 3) I posted the source without adding any newlines. So my question would be how it became a two-lie string in your decrypt. BUT in a spirit of co-operation I have changed the reference implementation source to: fprintf(stderr, "Usage scos2 mode keybase keyinc\n" "sci.crypt open secret.\n" "Encrypts stdin and writes on stdout" " - mode e encrypts, d decrypts.\n"); which is, of course, a single-line string, once Translation Phase 6 has done its thing: 6. Adjacent string literal tokens are concatenated. -- Richard Heathfield Email: rjh at cpax dot org dot uk "Usenet is a strange place" - dmr 29 July 1999 Sig line 4 vacant - apply within