Re: Incorrect requirements --- Computing the mapping from the input to HHH(DD)

On 09/05/2025 06:18, Keith Thompson wrote:

Richard Heathfield <rjh@cpax.org.uk> writes:

On 09/05/2025 00:53, olcott wrote:

On 5/8/2025 6:45 PM, Keith Thompson wrote:

[...]

I have no particular problem with that, but your failure to correct
a number of C errors in your code is odd.

As I already proved Microsoft reported no such errors.

>
That's tantamount to a claim of a bug in your compiler. Conforming C
compilers are /required/ to report syntax errors.

 Meh.  Most C compilers, certainly including gcc, clang, and
Microsoft's C compiler, are not conforming by default.  In fact,
I don't know of any that are.

Indeed, although it's normally quite easy to kick them into conforming mode if such a mode exists.
But when Mr Olcott directs the discussion towards the C language (and even cross-posts to comp.lang.c from time to time), it is reasonable to assume that he is talking about the C language. The C language is defined by an international standard, not by a set of command line switches.

I consider this unfortunate, but it means that if you want a
conforming C compiler, you need to use apply additional options
("-std=cNN -pedantic" for gcc and clang, and something else for
Microsoft's compiler).

It's been a very long time since I used a Microsoft compiler, but -W4 is worth a shot.

The problem, of course, is that different C compilers in their default
modes are lax in different ways, so an error that compiler X ignores by
default might become fatal when you use compiler Y.

Yes, which is fine as long as the compiler X user restricts himself to compiler X, but which can embarrass him if he starts making general claims about the language itself.
--
Richard Heathfield
Email: rjh at cpax dot org dot uk
"Usenet is a strange place" - dmr 29 July 1999
Sig line 4 vacant - apply within