Hi Hazen:
The propagation issue can be restated as follows: For all functions
where plexit is currently called (except possibly the memory
allocation issues which we might handle differently) you need to
propagate the return code backwards through the "caller graph". The
doxygen application uses t
On 2016-02-24 06:52-0500 Hazen Babcock wrote:
[Alan]
>> Anyhow, I am convinced by my above estimate that the propagation part
>> of the work will require similar effort to the rest of the project, I
>> do like the simplicity of the return code method that has proved to be
>> so useful in the ephco
On 2016-02-24 10:33- Phil Rosenberg wrote:
[Alan]
>> I believe there are some 300 functions in our public and private API,
>> and not all of those will be affected by this (because there are no
>> error conditions they generate or they need to propagate). So I would
>> estimate "hundreds" of f
On 2016-02-24 10:33- Phil Rosenberg wrote:
> Hi Alan
> I've cut and pasted some bits together of your last couple of emails
>
>
>
>> However, isn't being forced to use separate threads in order to
>> (automatically) have separate PLplot contexts for each thread a
>> relatively minor inconvenie
>
>> I obviously don't have any idea of the size of ephcom, but Plplot
> must have thousands of internal function calls that would need the
> return value checking.
>
> I believe there are some 300 functions in our public and private API,
> and not all of those will be affected by this (because
Hi Alan
I've cut and pasted some bits together of your last couple of emails
> However, isn't being forced to use separate threads in order to
> (automatically) have separate PLplot contexts for each thread a
> relatively minor inconvenience compared to the very much larger user
> inconvenience
On 2016-02-24 14:18+1030 Jonathan Woithe wrote:
> Hi Alan
>
> On Tue, Feb 23, 2016 at 11:00:24AM -0800, Alan W. Irwin wrote:
[..]
>> It appears everyone so far is happy with the context approach.
>> Furthermore, it appears now with thread-local storage that the address of
>> the context does not n
