From: KIMURA Masaru <hiyuh.root@gmail.com>
To: cygwin@cygwin.com
Subject: Re: __STRICT_ANSI__ and stdio.h
Date: Tue, 15 Dec 2015 15:58:00 -0000 [thread overview]
Message-ID: <CAPYQg30566rTTPhfbEbqEXV28043zAj80V5ppkz2z0ezQ5SRMw@mail.gmail.com> (raw)
In-Reply-To: <20151215093020.GA12827@calimero.vinschen.de>
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/freebsd/freebsd/blob/master/include/stdio.h
>> https://github.com/freebsd/freebsd/blob/master/sys/sys/cdefs.h
>>
>> it looks very different to newlib's.
>
> Yes, it does. Newlib has a long history diverging from the BSDs to
> support embedded systems in the first place, and compatibility checking
> macros other than __STRICT_ANSI__ and __POSIX_SOURCE weren't much of a
> concern for a long time.
>
>> FreeBSD has visibility for popen()/pclose() if __POSIX_VISIBLE >= 199209,
>> it looks no checking about __STRICT_ANSI__ in their cdefs.h.
>
> Yeah, that's history as described above. popen gets declared in newlib
> if __STRICT_ANSI__ is not defined right now.
>
>> only one thing i worried about is _ANSI_SOURCE in their cdefs.h,
>> (b/c i don't understand where _ANSI_SOURCE comes from...)
>> but it looks _POSIX_C_SOURCE wins anyway.
>> for ease to see, i'd attach simplified their cdefs.h for their
>> visibility handling.
>
> I don't see the difference, see below. The big differences in newlib
> are the additional handling of _GNU_SOURCE and the old usage of
> __STRICT_ANSI__ in some circumstances which haven't been replaced by another
> usage of compatibility macros yet.
>
> But here's the deal: Newlib is a volunteer-driven project. If the
> compatiblity checking macros are not correct or not correctly used in
> all circumstances, newlib is happily open to patches. Just send them
> to the newlib AT sourceware DOT org mailing list.
>
>> #if defined(_POSIX_C_SOURCE) && _POSIX_C_SOURCE == 1
>> #undef _POSIX_C_SOURCE
>> #define _POSIX_C_SOURCE 199009
>> #endif
>
> Same in Newlib's sys/cdefs.h.
>
> [SNIP]
ah, i didn't check newlib's sys/cdefs.h.
thank you for correcting my misunderstanding.
apart from standard compliance correctness,
it's good to hear newlib can deal it.
if i had more spare time to dive its source, i'd like to do it.
Peace,
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2015-12-15 15:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-12 7:51 KIMURA Masaru
2015-12-13 16:51 ` cyg Simple
2015-12-14 4:56 ` KIMURA Masaru
2015-12-14 4:58 ` KIMURA Masaru
2015-12-14 13:34 ` cyg Simple
2015-12-14 14:06 ` Corinna Vinschen
2015-12-14 17:17 ` KIMURA Masaru
2015-12-15 9:30 ` Corinna Vinschen
2015-12-15 15:58 ` KIMURA Masaru [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPYQg30566rTTPhfbEbqEXV28043zAj80V5ppkz2z0ezQ5SRMw@mail.gmail.com \
--to=hiyuh.root@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).