A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1647 ====================================================================== Reported By: eblake Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 Issue ID: 1647 Category: System Interfaces Type: Clarification Requested Severity: Objection Priority: normal Status: Interpretation Required Name: Eric Blake Organization: Red Hat User Reference: ebb.printf %lc Section: fprintf Page Number: 913 Line Number: 30957 Interp Status: Proposed Final Accepted Text: https://austingroupbugs.net/view.php?id=1647#c6239 ====================================================================== Date Submitted: 2023-03-28 16:32 UTC Last Modified: 2023-06-23 16:19 UTC ====================================================================== Summary: printf("%lc", (wint_t)0) can't output NUL byte ====================================================================== Relationships ID Summary ---------------------------------------------------------------------- related to 0001643 fprintf %lc: wrong reference to the cur... ======================================================================
---------------------------------------------------------------------- (0006346) geoffclare (manager) - 2023-06-23 16:19 https://austingroupbugs.net/view.php?id=1647#c6346 ---------------------------------------------------------------------- Re https://austingroupbugs.net/view.php?id=1647#c6251 Where does the Issue 8 draft say that the c17 utility has to provide a conforming C17 environment? I only see a requirement for it to "accept source code conforming to the ISO C standard", which is not the same thing. Also, conforming applications are required to define _POSIX_C_SOURCE (for POSIX-conforming applications) or _XOPEN_SOURCE (for XSI-conforming applications) so I don't see why POSIX would even try to specify how an implementation behaves when applications are compiled without defining one of those macros. Issue History Date Modified Username Field Change ====================================================================== 2023-03-28 16:32 eblake New Issue 2023-03-28 16:32 eblake Name => Eric Blake 2023-03-28 16:32 eblake Organization => Red Hat 2023-03-28 16:32 eblake User Reference => ebb.printf %lc 2023-03-28 16:32 eblake Section => fprintf 2023-03-28 16:32 eblake Page Number => 913 2023-03-28 16:32 eblake Line Number => 30957 2023-03-28 16:32 eblake Interp Status => --- 2023-03-28 16:32 eblake Relationship added child of 0001643 2023-03-28 16:33 eblake Desired Action Updated 2023-03-28 17:02 eblake Desired Action Updated 2023-03-28 17:30 eblake Note Added: 0006237 2023-03-28 17:31 eblake Description Updated 2023-03-28 17:37 eblake Desired Action Updated 2023-03-30 16:33 eblake Note Added: 0006239 2023-03-30 17:14 eblake Tag Attached: tc3-2008 2023-03-30 17:14 eblake Tag Attached: issue8 2023-04-03 15:27 eblake Note Added: 0006246 2023-04-03 15:28 eblake Note Edited: 0006239 2023-04-03 15:28 geoffclare Tag Detached: tc3-2008 2023-04-03 15:31 ajosey Interp Status --- => Pending 2023-04-03 15:31 ajosey Final Accepted Text => https://austingroupbugs.net/view.php?id=1647#c6239 2023-04-03 15:31 ajosey Resolution Open => Accepted As Marked 2023-04-03 15:32 ajosey Status New => Interpretation Required 2023-04-03 16:31 ajosey Note Added: 0006248 2023-04-03 16:31 ajosey Status Interpretation Required => Resolution Proposed 2023-04-03 16:46 hvd Note Added: 0006251 2023-04-03 17:15 ajosey Interp Status Pending => Proposed 2023-04-03 17:15 ajosey Status Resolution Proposed => Interpretation Required 2023-04-20 16:22 geoffclare Relationship replaced related to 0001643 2023-06-23 16:19 geoffclare Note Added: 0006346 ======================================================================
