Path: csiph.com!weretis.net!feeder8.news.weretis.net!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Tim Rentsch <tr.17687@z991.linuxsc.com>
Newsgroups: comp.lang.c
Subject: Re: C vs Haskell for XML parsing
Date: Wed, 30 Aug 2023 20:50:27 -0700
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <86msy7uayk.fsf@linuxsc.com>
References: <576801fa-2842-40dc-bf19-221a5b1cf660n@googlegroups.com> <639e8e6f-2729-476b-9a6e-0b3eb066b06an@googlegroups.com> <uc9m7v$3u797$1@dont-email.me> <d3c6df71-7ef5-4fd3-83be-8b9a4315f0c4n@googlegroups.com> <j=2ifExxFfXU05g0F@bongo-ra.co> <ae3d2d4e-71bd-4c6c-99aa-cf8b6b652175n@googlegroups.com> <87pm3bot1n.fsf@bsb.me.uk> <7a9b3883-ee9f-4d46-944c-c11d4f0354d5n@googlegroups.com> <ucdcaf$mj8h$1@dont-email.me> <627cbd87-75d6-49e9-b2e0-733ca17b7cean@googlegroups.com> <ucftjs$186cs$1@dont-email.me> <gN1HM.144949$ftCb.130257@fx34.iad> <86il8ywyu5.fsf@linuxsc.com> <uck607$2563l$1@dont-email.me> <20230829121430.516@kylheku.com> <ucnkde$2op2r$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: dont-email.me; posting-host="49a0c7fba7d7c0f06cea865d80b29294"; logging-data="3268288"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/2zxoa9j1Yk43kPoR0sf1aRNJUeAE75lQ="
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.4 (gnu/linux)
Cancel-Lock: sha1:kLQDMFwR2WehNlpRmiFuNOo8PW0= sha1:wqfmw+6ahP9+3zJ4lx+O/z6IG4I=
Xref: csiph.com comp.lang.c:173369

Lew Pitcher <lew.pitcher@digitalfreehold.ca> writes:

> On Tue, 29 Aug 2023 19:22:09 +0000, Kaz Kylheku wrote:
>
>> On 2023-08-29, David Brown <david.brown@hesbynett.no> wrote:
>>
>>> On 29/08/2023 01:07, Tim Rentsch wrote:
>>>
>>>> scott@slp53.sl.home (Scott Lurndal) writes:
>>>>
>>>>> I will use [underscore] in preference to CamelCase, which I
>>>>> dislike primarily because of the impact on my typing speed.
>>>>
>>>> In most cases I find CamelCase harder to read than using
>>>> underscores, especially when using mono-spaced fonts.
>>>
>>> I used to use camelCase for most of my identifiers - now I find I
>>> am using underscores much more, precisely because I find it easier
>>> to read.  I strongly suspect it is age-related - camelCase was
>>> more appealing when my eyes were younger.
>>
>> CamelCase is at odds with the C language.
>
> I would disagree.  CamelCase (as in identifiers consisting of a mix of
> upper and lower case characters) is inherent in the definition of an
> identifier, and has been since K&R C.  [...]

CamelCase is consistent with C syntax;  it feels out of place
though in terms of common usage.  ISTM that CamelCase was never
used in C until C++ started using it, which I think started
happening because Smalltalk uses camelCase (and CamelCase), and
C++ has Smalltalk envy.

Feel free to take the above either as just statements of
personal opinion or as unsubstantiated beliefs.