Re: __STRICT_ANSI__ and stdio.h

2015-12-15 Thread KIMURA Masaru
Hi, >> >> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to >> >> glibc's? >> > >> > Cygwin is using newlib, newlib is BSD based. We introduced the >> > compatibility checking macros from FreeBSD lately. >> >> i roughly checked FreeBSD include/stdio.h and sys/sys/cdefs.h. >>

Re: __STRICT_ANSI__ and stdio.h

2015-12-15 Thread Corinna Vinschen
On Dec 15 02:17, KIMURA Masaru wrote: > Hi, > > >> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to > >> glibc's? > > > > Cygwin is using newlib, newlib is BSD based. We introduced the > > compatibility checking macros from FreeBSD lately. > > i roughly checked FreeBSD incl

Re: __STRICT_ANSI__ and stdio.h

2015-12-14 Thread KIMURA Masaru
Hi, >> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to >> glibc's? > > Cygwin is using newlib, newlib is BSD based. We introduced the > compatibility checking macros from FreeBSD lately. i roughly checked FreeBSD include/stdio.h and sys/sys/cdefs.h. https://github.com/free

Re: __STRICT_ANSI__ and stdio.h

2015-12-14 Thread Corinna Vinschen
On Dec 12 16:51, KIMURA Masaru wrote: > Hi, > > is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to glibc's? Cygwin is using newlib, newlib is BSD based. We introduced the compatibility checking macros from FreeBSD lately. Corinna -- Corinna Vinschen Please

Re: __STRICT_ANSI__ and stdio.h

2015-12-14 Thread cyg Simple
On 12/13/2015 11:56 PM, KIMURA Masaru wrote: > Hi, > >>> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to >>> glibc's? >>> especially, i meant routines in POSIX 1003.1:2001 (popen(), pclose(), etc). >>> for a specific example, see a cparser issue[1] i submitted. >>> >> >> Cyg

Re: __STRICT_ANSI__ and stdio.h

2015-12-13 Thread KIMURA Masaru
oops! forgot to attach p.c, so resending now... > Hi, > >>> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to >>> glibc's? >>> especially, i meant routines in POSIX 1003.1:2001 (popen(), pclose(), etc). >>> for a specific example, see a cparser issue[1] i submitted. >>> >> >>

Re: __STRICT_ANSI__ and stdio.h

2015-12-13 Thread KIMURA Masaru
Hi, >> is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to >> glibc's? >> especially, i meant routines in POSIX 1003.1:2001 (popen(), pclose(), etc). >> for a specific example, see a cparser issue[1] i submitted. >> > > Cygwin isn't wrong. __STRICT_ANSI__ doesn't mix with POSIX

Re: __STRICT_ANSI__ and stdio.h

2015-12-13 Thread cyg Simple
On 12/12/2015 2:51 AM, KIMURA Masaru wrote: > Hi, > > is cygwin's __STRICT_ANSI__ and stdio.h behavior not so compatible to glibc's? > especially, i meant routines in POSIX 1003.1:2001 (popen(), pclose(), etc). > for a specific example, see a cparser issue[1] i submitted. > Cygwin isn't wrong.