Email List: Xaustin-group-lX
[All Lists]

Re: [Fwd: Re: Clearing environ]

To: austin-group-l@xxxxxxxxxxxxx
Subject: Re: [Fwd: Re: Clearing environ]
From: Geoff Clare <gwc@xxxxxxxxxxxxx>
Date: Fri, 1 Aug 2008 18:13:57 +0100
References: <1217604384.26163.32.camel@xxxxxx> <200808011542.m71Fgc2p002689@xxxxxx> <20080801160715.GA14327@xxxxxx> <200808011654.m71GsV9i005409@xxxxxx>
Glenn Fowler <gsf@xxxxxx> wrote, on 01 Aug 2008:
> 
> On Fri, 1 Aug 2008 17:07:15 +0100 Geoff Clare wrote:
> > Glenn Fowler <gsf@xxxxxx> wrote, on 01 Aug 2008:
> > > interesting that clearenv() is labeled non-standard and
> > > then used as part of a compliant solution
> 
> > Well, it does say it may be used "if available":
> 
> 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.

-- 
Geoff Clare <g.clare@xxxxxx>
The Open Group, Thames Tower, Station Road, Reading, RG1 1LX, England

<Prev in Thread] Current Thread [Next in Thread>