Re: [Fwd: Re: Clearing environ]

[Glenn Fowler <gsf@xxxxxxxxxxxxxxxx>]

On Fri, 1 Aug 2008 18:13:57 +0100 Geoff Clare wrote:
> Glenn Fowler <gsf@xxxxxx> wrote, on 01 Aug 2008:
> > I saw that and believe that "compliant" and "if available"
> > are mutually exclusive, i.e., compliance should be w.r.t.
> > the standard and not the output of ./configure

> I see what you mean.  It does seem a little odd at first, but it
> makes sense once you realise the heading "Compliant Solution" means
> the code complies with the CERT C Secure Coding Standard, whereas
> the "non-standard" label means the function is not in C99/POSIX.

thanks for clarifying the "compliant" and "non-standard" connections
I still don't buy it from a standards document though

is it wrong to think that "standard" obviates "./configure"?