Re: Adding a clockid_t parameter to functions that accept absolute timespecs

2018-11-27 Thread Tom Cherry
On Mon, Nov 26, 2018 at 10:20 AM Mike Crowe wrote: > > On Sunday 04 November 2018 at 10:32:38 +, Mike Crowe wrote: > > * Function naming: > > > > Several proposals have been made for naming: > > I only had one reply to the naming suggestions below, so I've combed > through prior emails

Re: Adding a clockid_t parameter to functions that accept absolute timespecs

2018-11-26 Thread Mike Crowe
On Sunday 04 November 2018 at 10:32:38 +, Mike Crowe wrote: > * Function naming: > > Several proposals have been made for naming: I only had one reply to the naming suggestions below, so I've combed through prior emails looking for preferences there. I apologise if I missed your preference.

Re: Adding a clockid_t parameter to functions that accept absolute timespecs

2018-11-04 Thread Daniel Eischen
> On Nov 4, 2018, at 5:32 AM, Mike Crowe wrote: > > * The problem: > > POSIX functions that take an absolute time point as a timeout parameter use > the CLOCK_REALTIME clock. This clock can be warped, particularly on > personal or embedded devices, which makes it unsuitable for use for >

Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads)

2018-10-29 Thread Tom Cherry
On Sat, Oct 27, 2018 at 5:16 PM Mark Harris wrote: > > On Sat, 27 Oct 2018 at 13:14, Mike Crowe wrote: >> >> On Saturday 27 October 2018 at 15:26:07 -0400, Daniel Eischen wrote: >> > >> > > On Oct 27, 2018, at 12:14 PM, Mike Crowe >> > > wrote: >> > > Looking through POSIX Base Specifications

Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads)

2018-10-27 Thread Mark Harris
On Sat, 27 Oct 2018 at 13:14, Mike Crowe wrote: > On Saturday 27 October 2018 at 15:26:07 -0400, Daniel Eischen wrote: > > > > > On Oct 27, 2018, at 12:14 PM, Mike Crowe > wrote: > > > Looking through POSIX Base Specifications Issue 7, I > > > believe that the following other functions lack a

Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads)

2018-10-27 Thread Mike Crowe
On Saturday 27 October 2018 at 17:07:00 -0400, Daniel Eischen wrote: > The nice thing about being able to set the clock in an attribute or some > other way (e.g., pthread_set_preferred_clock) is that you only have to do > it once, as opposed to potentially modifying lots of other code, even in >

Re: Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads)

2018-10-27 Thread Daniel Eischen
> On Oct 27, 2018, at 4:13 PM, Mike Crowe wrote: > >> On Saturday 27 October 2018 at 15:26:07 -0400, Daniel Eischen wrote: >> >>> On Oct 27, 2018, at 12:14 PM, Mike Crowe >>> wrote: >>> Looking through POSIX Base Specifications Issue 7, I >>> believe that the following other functions lack

Adding a clockid_t parameter to functions that accept absolute timespecs (was Re: C++ condition_variable and timed_mutex with steady_clock and pthreads)

2018-10-27 Thread Mike Crowe
On Saturday 27 October 2018 at 15:26:07 -0400, Daniel Eischen wrote: > > > On Oct 27, 2018, at 12:14 PM, Mike Crowe > > wrote: > > Looking through POSIX Base Specifications Issue 7, I > > believe that the following other functions lack a way to use > > CLOCK_MONOTONIC directly (and unlike