Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: isspace() executes without ctype header? Date: Wed, 14 Jun 2017 12:12:31 -0700 Organization: None to speak of Lines: 29 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="96bbf95725af2559ab0735ee54475e20"; logging-data="3357"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Qh7C5LyeD9MrG7s/DmzVW" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:SdFpSwwDfkd1dh/6vFXrBY/CbJA= sha1:z6FcPe662E/d40EI9ZGbQVDAfaw= Xref: csiph.com comp.lang.c:112215 bartc writes: > On 14/06/2017 18:21, Keith Thompson wrote: >> bartc writes: >>> C90 was at fault too. Why allow something so sloppy? And potentially >>> dangerous. >> >> Yes, the C90's implicit int rule was a problem. That problem was solved >> 18 years ago by removing the implicit int rule in C99. Not all >> compilers conform to C99 or C11 requirements. > > Funny way of solving it, by either ignoring it or reporting a mere > warning. All with compilers that have latest versions long after 1999. Not all compilers produced after 1999 conform to the C99 or C11 standard, and a non-fatal warning satisfies the standard's requirement for a diagnostic. Many compilers have an option to make such diagnostics fatal. If a warning isn't good enough for you, find out how to make the error fatal. Use a different compiler if necessary. If a compiler claims to conform to C99 and doesn't issue at least a warning, submit a bug report -- to the compiler provider, not to comp.lang.c. [...] -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"