Email List: Xaustin-group-lX
[All Lists]

Re: ISO C Defect Reports

To: Nick Stoughton <yyyy@xxxxxxxxxx>
Subject: Re: ISO C Defect Reports
From: Paul Eggert <yyyyyy@xxxxxxxxxxx>
Date: Fri, 05 May 2006 23:32:53 -0700
Cc: yyyyyyyyyyyyyy@xxxxxxxxxxxxx
References: <1146584748.21617.74.camel@xxxxxx>
Nick Stoughton <yyyy@xxxxxxxxxx> writes:

> http://www.open-std.org/jtc1/sc22/wg14/www/docs/summary.htm
>
> Since POSIX is firmly anchored in C, and as several parts of the C
> standard are included in POSIX, we all need to check through this list

It's a big list.  To save time, can we presume we don't need to check
defect report #285 and earlier?  #285 is the highest-numbered one that
was published in TC2.

I briefly reviewed defect reports #286 and up, and the biggest concern
I have with it is with respect to XCU ERN 76 (trailing white space and
CR in C source files).  XCU ERN 76 is marked as OPEN with "This is
also expected to be discussed at the ISO C meeting next week", but
I don't see it mentioned in any of the defect reports.

To refresh your memory, here's the last email (dated September 2005)
about XCU ERN 76 on austin-group-l.

https://www.opengroup.org/sophocles/show_mail.tpl?CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=8629

My feeling is that we don't need to consult with the ISO C committee
about this, since it's purely an issue about what the c99 command
does.  If so, we can go ahead and resolve this one, thus removing the
OPEN marking on it.  But if I'm wrong, then we need to file an ISO C
defect report.

<Prev in Thread] Current Thread [Next in Thread>