Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: Richard Heathfield <rjh@cpax.org.uk>
Newsgroups: comp.lang.c
Subject: Re: Which code style do you prefer the most?
Date: Sun, 2 Mar 2025 09:35:01 +0000
Organization: Fix this later
Lines: 57
Message-ID: <vq18o5$neo2$2@dont-email.me>
References: <vpkmq0$21php$1@dont-email.me> <vplhc7$26ur1$3@dont-email.me>
 <87v7swzzl7.fsf@onesoftnet.eu.org> <vpn4qi$2j0hq$1@dont-email.me>
 <vpo20n$2o9ks$1@dont-email.me> <vpo7ec$2ovro$1@dont-email.me>
 <87a5a7k0ko.fsf@onesoftnet.eu.org> <vpprv6$34o4m$2@dont-email.me>
 <8734fzozd2.fsf@nosuchdomain.example.com> <vprv83$3jah9$4@dont-email.me>
 <vps2sj$3k722$2@dont-email.me> <vps8n1$3l1rq$2@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 02 Mar 2025 10:35:01 +0100 (CET)
Injection-Info: dont-email.me; posting-host="466d76f997a1f90e214f6b0baca6a13f";
	logging-data="768770"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/pX58hTij4dN5PJid4rmI+vlZBB9ewUmWpQ9jHGsaW9w=="
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:CAWPI1rA78jrfGyoHXYQsdIIYm4=
In-Reply-To: <vps8n1$3l1rq$2@dont-email.me>
Content-Language: en-GB
Bytes: 3468

On 28/02/2025 12:03, David Brown wrote:
> On 28/02/2025 11:24, Richard Heathfield wrote:
>> On 28/02/2025 09:22, David Brown wrote:
>>> On 27/02/2025 22:24, Keith Thompson wrote:
>>>> Richard Heathfield <rjh@cpax.org.uk> writes:
>>>>> On 27/02/2025 12:56, Ar Rakin wrote:
>>>>>> bart <bc@freeuk.com> writes:
>>>>>>
>>>>>>> // isn't devoid of quirks (this is still C after all), for 
>>>>>>> example:
>>>>>>>
>>>>>>>      fopen(file,"rb");   // open file in \windows\system32\
>>>>>>>      fread(...);
>>>>>>>
>>>>>>> Here, the // line continues onto the next, so that the 
>>>>>>> fread is
>>>>>>> commented out. But they are fewer.
>>>>>> Interesting. Isn't this considered a compiler bug?
>>>>>
>>>>> No. Line splicing occurs in Translation Phase 2. Comment 
>>>>> removal
>>>>> doesn't happen until Translation Phase3. If a compiler 
>>>>> /didn't/ splice
>>>>> those lines, /that/ would be a bug.
>>>>
>>>> <OT>Long time no see.  Welcome back!</OT>
>>>>
>>>
>>> As long as it's not "Long time no C" :-)
>>
>> I'm afraid it is. Nowadays I spend most of my time arguing with 
>> \LaTeX, although when I do cut code it is in C (and that's 
>> proper C, of course, not this newfangled gibberish).
>>
> 
> LaTeX is great when it's all going well, but sometimes macros can 
> get pretty hairy - I've written more than my share of unreadable 
> macro code.  There's also the risk that you spend so much time 
> examining the microtyping and ligature generation at 1600% zoom 
> on the pdf reader, that you don't have time to write the documents!

Quite. Have you ever given up entirely and settled for a 
re-wording? That's my t-shirt.

> Still, LaTeX (or LuaLaTeX, as I use these days) is better than 
> anything else I know of.

One of its best features is *not* allowing footnotes to have 
footnotes. This feature has saved not only many hours but quite 
possibly my eyesight.

-- 
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