A NOTE has been added to this issue. ====================================================================== https://austingroupbugs.net/view.php?id=1614 ====================================================================== Reported By: kre Assigned To: ====================================================================== Project: 1003.1(2016/18)/Issue7+TC2 Issue ID: 1614 Category: System Interfaces Type: Omission Severity: Objection Priority: normal Status: New Name: Robert Elz Organization: User Reference: Section: XSH 3/mktime Page Number: 1331 Line Number: 44331-44332 Interp Status: --- Final Accepted Text: ====================================================================== Date Submitted: 2022-11-03 13:36 UTC Last Modified: 2022-11-07 12:42 UTC ====================================================================== Summary: XSH 3/mktime does not specify EINVAL and should ======================================================================
---------------------------------------------------------------------- (0006035) geoffclare (manager) - 2022-11-07 12:42 https://austingroupbugs.net/view.php?id=1614#c6035 ---------------------------------------------------------------------- Re https://austingroupbugs.net/view.php?id=1614#c6033 > The footnote makes it clear that this is considered to follow from the > normative wording and there is therefore no need to have this as a separate > requirement in the normative wording; the footnote is merely for > clarification. I believe that thinking here is correct. Do you disagree? Yes I disagree. The word "thus" is what makes it seems like this follows from normative text, but if you look at the normative text where the footnote marker is, there is nothing there from which the text in the footnote could be derived. So the use of "thus" is puzzling. I believe the real reason that the text is in a footnote instead of normative is because, earlier on, the C standard says "The local time zone and Daylight Saving Time are implementation-defined." Since DST is implementation-defined the C standard can't have normative text requiring mktime() to behave a certain way with regard to DST; it is left to implementations to decide how to interpret tm_isdst. In POSIX the DST rules are specified in the description of TZ, so there is no problem requiring mktime() to make use of them. Issue History Date Modified Username Field Change ====================================================================== 2022-11-03 13:36 kre New Issue 2022-11-03 13:36 kre Name => Robert Elz 2022-11-03 13:36 kre Section => XSH 3/mktime 2022-11-03 13:36 kre Page Number => 1331 2022-11-03 13:36 kre Line Number => 44331-44332 2022-11-03 16:54 geoffclare Note Added: 0006022 2022-11-03 18:04 hvd Note Added: 0006025 2022-11-03 20:02 kre Note Added: 0006028 2022-11-03 20:27 kre Note Added: 0006030 2022-11-03 20:43 kre Note Edited: 0006028 2022-11-03 20:48 kre Note Edited: 0006028 2022-11-04 09:36 geoffclare Note Added: 0006031 2022-11-04 10:01 geoffclare Note Edited: 0006031 2022-11-04 17:37 kre Note Added: 0006032 2022-11-04 17:43 kre Note Edited: 0006032 2022-11-04 23:23 hvd Note Added: 0006033 2022-11-04 23:23 hvd Note Edited: 0006033 2022-11-07 12:33 geoffclare Note Added: 0006034 2022-11-07 12:42 geoffclare Note Added: 0006035 ======================================================================
