Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Tim Rentsch Newsgroups: comp.lang.c Subject: Re: K&R, 2nd edition, Brian's concerns with ``char c = EOF'' Date: Wed, 08 Dec 2021 19:23:08 -0800 Organization: A noiseless patient Spider Lines: 37 Message-ID: <86fsr28ns3.fsf@linuxsc.com> References: <86pmqwkm7u.fsf@levado.to> <4fcda596-2e00-4dd6-bf8f-4616218f4398n@googlegroups.com> <91a56855-b917-45a2-89be-7e2ed806d357n@googlegroups.com> <87a6hac0oj.fsf@nosuchdomain.example.com> <11efb602-293a-4a90-b0bd-832617377f57n@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="0305535afcf6543e663c79d2b7a9e067"; logging-data="17965"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+SvrkI526Pa5XChQDP6xrVfUBTfvmyyFw=" User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux) Cancel-Lock: sha1:G1iRYRAVLTJRHqlpWt5EgVFiijU= sha1:uR1tBGThIaZpMAPUHjFYayLVx7c= Xref: csiph.com comp.lang.c:163736 Dave Dunfield writes: > On Wednesday, December 8, 2021 at 3:16:25 PM UTC-5, Keith Thompson wrote: > >>> In case anyone wants to look at: TEST.C >>> This file is ENCTXTed to protect from online reformatting. >>> To Decode get: Daves Old Computers->Personal->Downloads->ENCTXT >>> ... >> >> I don't think many people are going to download EXCTXT so they can >> decode your source file. >> >> You can just include code inline in a post. As long as the lines aren't >> too long it shouldn't be a problem. > > Unfortunately, I only have access to newsgroups now through "google > groups" which horrendously re-formats any text I post... C source > I've tried to post "inline" always comes out horrible: Spacing > removed, lines joined etc. > > ENCTXT is an easy way to get the original text, doesn't have to be > "installed" etc, I include a DVM binary (which can work on Win or > Linux "as is") but also the full C source code which I have > confirmed compiles (and works correctly) with Micro-C, LCC and GCC > (and probably lots of other compilers) so you can see exactly how it > works and what it does... and compile it yourself "to be sure". Please either post the code directly or post it in base64. The cryptic directions for how to get ENCTXT are, at least for me, completely useless. Or if you want post the .c code for ENCTXT, and let other people worry about taking care of google groups formatting screwups. (Incidentally, can you explain why you can't set up a news account with one of several few news providers, such as eternal-september, and avoid the problems of using google groups?)