On 2016-02-23 00:50-0500 Jim Dishaw wrote:
>
>> On Feb 22, 2016, at 5:48 PM, Alan W. Irwin wrote:
>>
>> @Everybody: now on to my C idea for thread safety.
>>
>> My idea for implementing that (closely following what was done for the
>> C ephcom library case where David Howells implemented an ephco
Hi Alan and Jim
I entirely advocate this. This is the same model that libcurl uses
too. In libcurl the "context" variable is a typecast void* so is
entirely opaque to the user, but it gets cast to a structure
internally. I presume the idea would be that the user would use one
context per thread?
T
> On Feb 22, 2016, at 5:48 PM, Alan W. Irwin wrote:
>
> @Everybody: now on to my C idea for thread safety.
>
> My idea for implementing that (closely following what was done for the
> C ephcom library case where David Howells implemented an ephcom
> context to help provide an API that did not d
@Phil: I am particularly interested in your reaction here because you
had the idea before that you could implement PLplot in a thread-safe
way by using C++ as the core language, i.e., rewriting PLplot in C++.
I don't rule out the possibility, but one intermediate step toward
that goal might be to i
