On 13 August 2012 18:49, Jonathan Wakely wrote:
> I suppose EOPNOTSUPP might be better, if it's supported everywhere.
> EPERM has the advantage of being a documented error for
> pthread_create.
We do define std::errc::operation_not_supported unconditionally on
most platforms, but not mingw or djgp
On 13 August 2012 16:47, Joe Buck wrote:
> On Sun, Aug 12, 2012 at 08:02:30PM +0100, Jonathan Wakely wrote:
>> This improves the fairly uninformative "Operation not supported"
>> message given when std::thread is used without linking to libpthread.
>>
>> Now you get:
>>
>> terminate called after t
On Sun, Aug 12, 2012 at 08:02:30PM +0100, Jonathan Wakely wrote:
> This improves the fairly uninformative "Operation not supported"
> message given when std::thread is used without linking to libpthread.
>
> Now you get:
>
> terminate called after throwing an instance of 'std::system_error'
> w
This improves the fairly uninformative "Operation not supported"
message given when std::thread is used without linking to libpthread.
Now you get:
terminate called after throwing an instance of 'std::system_error'
what(): Enable multithreading to use std::thread: Operation not permitted
Abort
