bug-wget
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Windows: stdout isn't properly set to binary mode


From: Ray Satiro
Subject: Re: [Bug-wget] Windows: stdout isn't properly set to binary mode
Date: Thu, 13 Jan 2011 20:29:44 -0800 (PST)

--- On Thu, 1/13/11, Micah Cowan <address@hidden> wrote:

> From: Micah Cowan <address@hidden>
> Subject: Re: [Bug-wget] Windows: stdout isn't properly set to binary mode
> To: "Ray Satiro" <address@hidden>
> Cc: address@hidden
> Date: Thursday, January 13, 2011, 11:20 PM
> On 01/13/2011 11:42 AM, Ray Satiro
> wrote:
> > This is true, NULL is not a valid parameter for
> freopen(), f etc, in
> > windows. Generally speaking with concern to all API
> all parameters must
> ? be valid and cannot be NULL unless explicitly permitted.
> For example,
> > free(NULL) is ok because the C standard explicitly
> permits it.
> 
> FWIW, NULL is in fact explicitly permitted as a parameter
> value for
> freopen() by the C standard; at least it has been for the
> last 12 years.
> Not that anyone (Microsoft in particular) pays attention to
> the 1999 C
> standard, I guess.
> 

Micah,

Yes you bring up a good point. C99 explicitly permits it, not C89/C90. MSVC is 
not C99 compliant and from what I've read there are no plans to make it so. 

Jay



      



reply via email to

[Prev in Thread] Current Thread [Next in Thread]