Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Philip Guenther via austin-group-l at The Open Group
I agree with Robert on this. Bumping the value of these macros when there's no change to the specified behavior of the relevant functionality provides no benefit and is actively harmful to code being forward portable. Yes, this makes the text of the specification for these more complex, while bum

Re: [1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Paul Smith via austin-group-l at The Open Group
On Fri, 2020-12-04 at 02:44 +0700, Robert Elz via austin-group-l at The Open Group wrote: > | The fact that bmake prints a warning if you try to "overwrite" a rule > | is another hint that my proposal to first require an explicit removal > | with the same pattern and no command before permitt

Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Robert Elz via austin-group-l at The Open Group
Date:Thu, 3 Dec 2020 20:08:35 + (UTC) From:shwaresyst Message-ID: <542954052.4149333.1607026115...@mail.yahoo.com> | It's my understanding the practice predates Issue 6 | and stems from a desire to not break code similar to: | #include | #if defined(POSIX

Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread shwaresyst via austin-group-l at The Open Group
It's my understanding the practice predates Issue 6 (I just used that as example) and stems from a desire to not break code similar to: #include #if defined(POSIX_OPT) && POSIX_OPT == _POSIX_VERSION ... Add code that presumes option availability ... #endif or at runtime: #ifdef POSIX_OPT if sys

Re: [1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Robert Elz via austin-group-l at The Open Group
Date:Thu, 3 Dec 2020 18:43:13 + From:Austin Group Bug Tracker Message-ID: <2b7895fb8cafbe206e7246596b3d5...@www.austingroupbugs.net> | A NOTE has been added to this issue. I am replying on the list, rather than via another note, as this reply adds nothing of su

Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Robert Elz via austin-group-l at The Open Group
Date:Thu, 3 Dec 2020 10:53:43 -0800 From:Nick Stoughton Message-ID: | If the value is 200112L, then the implementation of the monotonic clock is | as specified in that version of the standard (where it was optional). If | the value is 200809L, then the impleme

Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Nick Stoughton via austin-group-l at The Open Group
If the value is 200112L, then the implementation of the monotonic clock is as specified in that version of the standard (where it was optional). If the value is 200809L, then the implementation of the monotonic clock is as specified in that version (where it was optional). And so on ... The introd

[1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=513 == Reported By:dwheeler Assigned To:a

Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Robert Elz via austin-group-l at The Open Group
Date:Thu, 3 Dec 2020 18:11:51 + (UTC) From:shwaresyst Message-ID: <684426419.4103424.1607019111...@mail.yahoo.com> | The 20yymmL shall be replaced with the value specific to Issue 8 when that | is finalized, not that an implementation may choose an arbitrary v

Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread shwaresyst via austin-group-l at The Open Group
The 20yymmL shall be replaced with the value specific to Issue 8 when that is finalized, not that an implementation may choose an arbitrary value after 2000. It's a placeholder to indicate this for the bug report only. The other 200809L values all get a blanket change eventually too, consistent

Re: [1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Robert Elz via austin-group-l at The Open Group
Date:Thu, 3 Dec 2020 17:21:47 + From:"Austin Group Bug Tracker via austin-group-l at The Open Group" Message-ID: | A NOTE has been added to this issue The issue is now closed, so I cannot append a new note [Aside: adding proposed text, and immediately closing

[1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1346 == Reported By:markh Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001346]: Require support for CLOCK_MONOTONIC

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1346 == Reported By:markh Assigned To: ==

[1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=513 == Reported By:dwheeler Assigned To:a

[1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=513 == Reported By:dwheeler Assigned To:a

[1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=513 == Reported By:dwheeler Assigned To:a

[1003.1(2016/18)/Issue7+TC2 0001345]: date(1) default format

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
The following issue has been RESOLVED. == https://austingroupbugs.net/view.php?id=1345 == Reported By:j_willie Assigned To: =

[1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=513 == Reported By:dwheeler Assigned To:a

[1003.1(2008)/Issue 7 0000513]: Add pattern rules (metarules) to make

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=513 == Reported By:dwheeler Assigned To:a

[1003.1(2016/18)/Issue7+TC2 0001429]: recvfrom does not specify the errno on timeout when the SO_RCVTIMEO option has been set

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://www.austingroupbugs.net/view.php?id=1429 == Reported By:Konrad_Schwarz Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001429]: recvfrom does not specify the errno on timeout when the SO_RCVTIMEO option has been set

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1429 == Reported By:Konrad_Schwarz Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001429]: recvfrom does not specify the errno on timeout when the SO_RCVTIMEO option has been set

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1429 == Reported By:Konrad_Schwarz Assigned To:

[1003.1(2016/18)/Issue7+TC2 0001429]: recvfrom does not specify the errno on timeout when the SO_RCVTIMEO option has been set

2020-12-03 Thread Austin Group Bug Tracker via austin-group-l at The Open Group
A NOTE has been added to this issue. == https://austingroupbugs.net/view.php?id=1429 == Reported By:Konrad_Schwarz Assigned To: