Path: csiph.com!news.swapon.de!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: Keith Thompson <kst-u@mib.org>
Newsgroups: comp.lang.c
Subject: Re: C Translator
Date: Mon, 01 Apr 2019 13:41:11 -0700
Organization: None to speak of
Lines: 37
Message-ID: <ln4l7ha26w.fsf@kst-u.example.com>
References: <Dr6nE.1476625$Xct1.1108593@fx12.am4> <87y34yc67j.fsf@bsb.me.uk> <MKnnE.266499$kh.234296@fx27.am4> <87lg0xbg9y.fsf@bsb.me.uk> <dRvnE.1488903$Xct1.1048418@fx12.am4> <5c9ef544.996282798@core> <_1InE.230560$MT2.63924@fx21.am4> <5c9f93d9.1036879283@core> <sGOnE.949299$Apg.157218@fx36.am4> <87o95s9k7v.fsf@bsb.me.uk> <JjSnE.1260288$OGY.1140038@fx08.am4> <87imvzaiis.fsf@bsb.me.uk> <jG1oE.282641$kh.152691@fx27.am4> <877ecf9lyv.fsf@bsb.me.uk> <dW4oE.682614$ao.267556@fx32.am4> <q7r3rg$ua7$1@dont-email.me> <lZ8oE.867468$iV1.117974@fx25.am4> <q7rcue$l6c$1@dont-email.me> <_DdoE.513530$7F3.198430@fx30.am4> <q7sm0e$mpm$2@dont-email.me> <UuqoE.446198$P_2.104203@fx26.am4>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Injection-Info: reader02.eternal-september.org; posting-host="29c90be48bf013696436a23e550ceb9e"; logging-data="11410"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX19ls/qocMCRqNnLuTEXIatu"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux)
Cancel-Lock: sha1:6I5Ny51TRd2kKUMtLkQzbZSe2ZM= sha1:33I7Ut697A1Qkpcq+IKoyRcqF5I=
Xref: csiph.com comp.lang.c:142703

Bart <bc@freeuk.com> writes:
> On 01/04/2019 10:35, David Brown wrote:
>> On 01/04/2019 03:16, Bart wrote:
>>> The trouble is that no one writes to precise guidelines like this, as I
>>> do
>
>> You think you are the only person that writes coding guidelines?  What
>> planet do you live on?
>
> A planet where I encounter other people's code. Lots of it.
>
> What guidelines do you think this program is using:
>
>    https://github.com/sal55/qx/blob/master/lisp.c
>
> (This works with some compilers, but not mine. The first problem is that 
> it's comparing pointers with ints (ie. ptr<int) which I don't allow, and 
> I'm not prepared to change that.

I'll probably regret asking this, but how is that code relevant?

(It's 503 lines of obfuscated C code that results in dozens of
diagnostic messages when I compile it.  Most of the warnings are for bad
integer/pointer casts.  It also fails to include the required headers
for write() and waitpid(), and uses a function I've never heard of
called "strf".)

> There are others, but I now no longer get drawn into pointless exercises 
> like this where the other side - the author of the code - is not 
> prepared to make some effort to write decent code.)

Bad code exists.  So what?

-- 
Keith Thompson (The_Other_Keith) kst-u@mib.org  <http://www.ghoti.net/~kst>
Will write code for food.
void Void(void) { Void(); } /* The recursive call of the void */