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,comp.lang.c++ Subject: Re: Switching to C# Date: Sat, 15 Jun 2019 19:31:13 -0700 Organization: None to speak of Lines: 15 Message-ID: References: <5d03bb38.3305609877@core> <5d059fdf.3429680737@core> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="df4904b93ef33b63818a6c0a0a5ba2e4"; logging-data="12742"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19axegBzydrjbDovc4wLZUg" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:Bi+LwZXdvfW2CfcdRzQ0+G4fL0s= sha1:0vKkA2w/idKchHIBy+SrvYPmGU0= Xref: csiph.com comp.lang.c:144909 comp.lang.c++:66456 nobody@example.org (Scott) writes: [...] > C does allow implicit declarations. You can call a previously > undeclared function, and C will trust that the types you're passing > are the types the function's expecting. I think it's a bad idea, and > it usually yields warnings suggesting that it's a bad idea. I think > any form of implicit typing is a bad idea. No, it doesn't. Calling an undeclared function has been a constraint violation since C99 dropped the "implicit int" rule. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Will write code for food. void Void(void) { Void(); } /* The recursive call of the void */