Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: C Translator Date: Mon, 01 Apr 2019 16:25:10 -0700 Organization: None to speak of Lines: 37 Message-ID: References: <87lg0xbg9y.fsf@bsb.me.uk> <5c9ef544.996282798@core> <_1InE.230560$MT2.63924@fx21.am4> <5c9f93d9.1036879283@core> <87o95s9k7v.fsf@bsb.me.uk> <87imvzaiis.fsf@bsb.me.uk> <877ecf9lyv.fsf@bsb.me.uk> <_DdoE.513530$7F3.198430@fx30.am4> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="a8aa2c8b7dd2955eccfe556864ca53e6"; logging-data="12363"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+fCHR+A6wSTV+x60dVaJEI" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:9+QEWGaA4BjIMuZnRyrgYQw306M= sha1:MF7oGXMPow6H3QDaLTuRlg16IGw= Xref: csiph.com comp.lang.c:142714 Bart writes: > On 01/04/2019 21:41, Keith Thompson wrote: >> Bart writes: >>> I'll probably regret asking this, but how is that code relevant? > > Because DB seems to think that everyone follows coding guidelines. This > is one example of many that doesn't. Not clear coding guidelines anyway. David Brown said no such thing. Here's his statement to which you responded: You think you are the only person that writes coding guidelines? What planet do you live on? Learn to read. [...] >> Bad code exists. So what? > > That doesn't tell you anything? Nothing that I didn't already know. [...] > Even if compilers allowed integer/pointer compares last century, there > is no reason to still allow it now. That means having a hard error. You know how to get a C compiler to treat it as a hard error. [...] -- Keith Thompson (The_Other_Keith) kst-u@mib.org Will write code for food. void Void(void) { Void(); } /* The recursive call of the void */