Re: [Threads-devel] boost::unique_lock<boost::mutex>::timed_lock --> win32 versus pthreads

Subject: Re: [Threads-devel] boost::unique_lock<boost::mutex>::timed_lock --> win32 versus pthreads
From: Geoff Shapiro (gshapiro_at_[hidden])
Date: 2010-05-12 11:37:40

Anthony Williams <anthony <at> justsoftwaresolutions.co.uk> writes:

> > Intentional? Oversight? I'm curious...
> 
> It's an oversight. It should be private inheritance and using directives.
> 
> Well spotted, thanks.
> 
> Anthony

Anthony, thanks for the quick response.

The only reason I caught this is because our new software development has to
work in both a win32 and VxWorks environment. The code, originally developed on
win32, was using the timed_lock interface on the unique_lock with a normal
mutex. Bad on us for not reading the doc carefully enough, but we found out the
error of our ways quite quickly once we started compiling in the VxWorks
pthreads environment!

Best regards,
Geoff Shapiro