DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=LIhtjaVha0vU4DeGmBewngh156Vu4
	hCzqpVmmLqDt9fHUinJATNjHNReh4l9vYby5b72YQ89UN+SEUjRYi6Fo3mmiR9qQ
	MxnuPb2iS5i2ov6F2GP6EodFppL5QxGOhJuCbGH3N92DEz7qwbbswgdkeiYGw3co
	ZZY1NJ8nN8kWH4=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
Date: Sat, 12 Dec 2015 16:51:16 +0900
Message-ID: <CAPYQg31yUkpu9oC1cfWTmxaBANBYcd4X18RY9Q+BVpx-o=nLBw@mail.gmail.com>
Subject: __STRICT_ANSI__ and stdio.h
From: KIMURA Masaru <hiyuh.root@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

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.

Peace,
-----
[1] https://github.com/MatzeB/cparser/issues/10

--
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