From: Alan W. I. <ir...@be...> - 2016-02-24 17:18:46
|
On 2016-02-24 10:33-0000 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 inconvenience compared to the very much larger user >> inconvenience required by adding a context address to most API calls? >> > Not necessarily. This may force someone to restructure their code as > they would have to have separate contexts in separate functions and > may actually generate race conditions that people will need to deal > with using mutexes. Without introducing backwards incompatibilities in our entire API we could certainly add a getter, plgcontext and setter, plscontext, for PLplotContextAddress to our API similarly to the way that plgstrm and plsstrm work now. Alan __________________________ Alan W. Irwin Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca). Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net). __________________________ Linux-powered Science __________________________ |