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

Keith Thompson <Keith.S.Thompson+u@gmail.com> writes:
[...]

The standard does say that it does not specify "the size or
complexity of a program and its data that will exceed the capacity of
any specific data-processing system or the capacity of a particular
processor".  It doesn't explicitly say that a program that exceeds
the system's capacity has undefined behavior, but "Undefined behavior
is otherwise indicated in this document by the words "undefined
behavior" **or by the omission of any explicit definition of
behavior**" (emphasis added).

[...]

I misplaced a quotation mark and did not quote the entire relevant
paragraph.  To be painfully clear, the following is Section 4,
Paragraph 2 of the N3096 draft of the ISO C23 standard:

    If a "shall" or "shall not" requirement that appears outside of
    a constraint or runtime-constraint is violated, the behavior is
    undefined. Undefined behavior is otherwise indicated in this
    document by the words "undefined behavior" or by the omission
    of any explicit definition of behavior. There is no difference
    in emphasis among these three; they all describe "behavior that
    is undefined".

--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */