This e-mail is to provide a summary of what we had discussed, please let 
me know if I left anything out. I think we had a consensus that the 
following change would be made as part of a possible version 6:

1. All API functions return error codes.


I think we also agreed on these items, which might not actually require 
a major version bump as the actual change to the API is potentially 
small / nil:

2. Thread safety.

3. Improved text handling between core and the drivers.


And there was some discussion about whether this was a good idea:

4. Core handles some text rendering.


Now I think the question is if the effort and disruption involved in (1) 
justifies making the change. I would say that I'm neutral about this. I 
feel that it is the way a modern library should behave. However I'm not 
sure that the fact that PLplot does not currently work this way is 
actually causing a lot of problems for people.

-Hazen


------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to