ock
> > pthread_rwlock_timedrdlock_onclock
> > pthread_rwlock_timedwrlock_onclock
> > mq_timedreceive_onclock
> > mq_timedsend_onclock
> > pthread_cond_timedwait_onclock
>
> Preferred by Tom Cherry (although I suspect that, like me, he's be happy
> wi
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
> > >>
> > >>> On Wednesday 12 September 2018 at 13:47:59 -0700, Tom Cherry wrote:
> > >>>> On Wed, Sep 12, 2018 at 11:56 AM Mike Crowe
> > >>>> wrote:
> > >>>>>
> > >>>>> We (libc te
On Sun, Oct 7, 2018 at 6:09 AM Mike Crowe
wrote:
> On Saturday 06 October 2018 at 17:43:06 -0400, Daniel Eischen wrote:
> >
> > > On Oct 6, 2018, at 3:00 PM, Mike Crowe
> wrote:
> > >
> > > Thank you for your detailed responses and patch links. I'm sorry it's
> taken
> > > me so long to
On Wed, Sep 12, 2018 at 11:56 AM Mike Crowe wrote:
>
> On Wednesday 12 September 2018 at 11:29:26 -0700, Tom Cherry wrote:
> > On Sun, Sep 9, 2018 at 8:28 AM Mike Crowe
> > wrote:
> > >
> > > On Thursday 30 August 2018 at 21:10:48 +0100, Mike Crowe wrote:
>
On Sun, Sep 9, 2018 at 8:28 AM Mike Crowe wrote:
>
> On Thursday 30 August 2018 at 21:10:48 +0100, Mike Crowe wrote:
> > C++11's std::condition_variable, std::timed_mutex and
> > std::recursive_timed_mutex support waiting with a timeout specified using
> > an arbitrary clock. It's common to use
