On 2016-02-26 22:45-0500 Hazen Babcock wrote:
> On 02/26/2016 05:18 PM, Alan W. Irwin wrote:
[...]
>> But I have to admit you [Phil] have
>> already made a fairly convincing argument for error reporting via C
>> exception handling, and if you look at the caller graphs I prepared
>> there are some
On 02/26/2016 05:18 PM, Alan W. Irwin wrote:
> @Hazen:
>
> Please pay close attention to this ongoing discussion and participate
> in it further because I don't want you to start work on the return
> value approach for reporting errors like you have already volunteered
> to do just in case the (l
@Hazen:
Please pay close attention to this ongoing discussion and participate
in it further because I don't want you to start work on the return
value approach for reporting errors like you have already volunteered
to do just in case the (likely) decision is made that we go with error
reporting ba
On 2016-02-26 17:34- Phil Rosenberg wrote:
> We have discussed a few API breaking changes recently. Error
> reporting, thread safety, C++ API changes and the Fortran API changes
> are pretty close to complete by the seems of things.
>
> Is it time to bring up the possibility of PLPlot 6 again
We have discussed a few API breaking changes recently. Error
reporting, thread safety, C++ API changes and the Fortran API changes
are pretty close to complete by the seems of things.
Is it time to bring up the possibility of PLPlot 6 again and how we
intend to manage that?
Alan there are some fu
