Subj : Re: Non-strictly-conforming and unspecified versus undefined behavior
To   : comp.programming.threads,comp.std.c
From : David Schwartz
Date : Sat Feb 19 2005 01:44 pm


> All of that is beside the point. The claims I am making are:
>
> A. C99 imposes requirements for programs that are not strictly conforming.

    Doesn't matter, we're not talking about programs that are "not strictly 
conforming", we're talking about programs that invoke undefined behavior. It 
is logically impossible for a standard to impose requirements on programs 
that invoke undefined behavior.

> B. POSIX imposes requirements for programs that are not Strictly 
> Conforming
>    POSIX Applications.
>
> Therefore, it is incorrect to say that "Providing no strictly-conforming
> code can tell the difference, POSIX is silent." Nothing that Doug has said
> above contradicts this.

    You are correct. This should read "providing no program that doesn't 
invoke undefined behavior can tell the difference".

    DS

.