The stderr stream is a FILE *, not a file descriptor. While a FILE record can
make use of a descriptor, the C standard considers descriptors an extension,
not a requirement. So, it's arguable the historical implementation will not
compile or execute when __STDC_HOSTED__ is defined on a platform
A NOTE has been added to this issue.
==
http://austingroupbugs.net/view.php?id=1117
==
Reported By:geoffclare
Assigned To:
==
All
Enclosed are the minutes of this weeks meeting. The next meeting is July 12th.
regards
Andrew
Minutes of the 28th June 2018 Teleconference Austin-874 Page 1 of 1
Submitted by Andrew Josey, The Open Group. 29th June 2018
Attendees:
Mark Ziegast, SHware Systems Dev.
Nick Stough
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//opengroup.org//NONSGML kigkonsult.se iCalcreator 2.22.1//
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/New_York
X-LIC-LOCATION:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20120311T02
RRULE:FREQ=YE
"Schwarz, Konrad" wrote:
> I think you are confusing things.
>
> perror() writes to stderr, which is unbuffered by default, i.e. is "fairly
> fast".
Did you look into genetical UNIX code?
Jörg
--
EMail:jo...@schily.net(home) Jörg Schilling D-13353 Berlin
joerg.schill
> -Original Message-
> From: Joerg Schilling [mailto:joerg.schill...@fokus.fraunhofer.de]
> Sent: Friday, June 29, 2018 12:46 PM
> To: g...@opengroup.org; austin-group-l@opengroup.org
> Subject: Re: Historic perror() (was: perror() changes the orientation
> of stderr to byte-oriented mode
Geoff Clare wrote:
> I would say they had good reason: fixing a misfeature.
>
> If you freopen() stderr to be a plain file, then it becomes fully buffered
> and if perror() writes directly to fd 2 its output will appear in the file
> before characters that are already in the buffer. (Or are you
Joerg Schilling wrote, on 29 Jun 2018:
>
> Geoff Clare wrote:
>
> > Joerg Schilling wrote, on 29 Jun 2018:
> > >
> > > the historic implementation calls write(2) to STDERR_FILENO.
> >
> > The C Standard says that perror() writes to the standard error stream.
> > The historic implementation does
Geoff Clare wrote:
> Joerg Schilling wrote, on 29 Jun 2018:
> >
> > the historic implementation calls write(2) to STDERR_FILENO.
>
> The C Standard says that perror() writes to the standard error stream.
> The historic implementation does not conform to the C Standard.
Then the C standard is wr
Joerg Schilling wrote, on 29 Jun 2018:
>
> the historic implementation calls write(2) to STDERR_FILENO.
The C Standard says that perror() writes to the standard error stream.
The historic implementation does not conform to the C Standard.
--
Geoff Clare
The Open Group, Apex Plaza, Forbury Road
Eric Blake wrote:
> I'm forwarding an email originally sent to the Cygwin list. What do
> others think? Is there enough grounds in the argument below that the
> CX-shading in POSIX is too strict compared to existing implementations,
> and that I ought to open a bug to change the wording on the
Eric Blake wrote, on 28 Jun 2018:
>
> I'm forwarding an email originally sent to the Cygwin list. What do others
> think? Is there enough grounds in the argument below that the CX-shading in
> POSIX is too strict compared to existing implementations, and that I ought
> to open a bug to change the
12 matches
Mail list logo