Re: [Plplot-devel] The status of the wxwidgets IPC development

2017-02-13 Thread Alan W. Irwin
On 2017-02-13 20:24- p.d.rosenb...@gmail.com wrote: > I have absolutely no efficiency concerns. The cpu cycles will be totally negligible compared to the time to copy the memory. To be honest I rarely stress about efficiency. Premature optimisation is usually a bad thing – don't forget that th

Re: [Plplot-devel] The status of the wxwidgets IPC development

2017-02-13 Thread p.d.rosenberg
I have absolutely no efficiency concerns. The cpu cycles will be totally negligible compared to the time to copy the memory. To be honest I rarely stress about efficiency. Premature optimisation is usually a bad thing – don't forget that the compiler has the ability to totally optimise away your

Re: [Plplot-devel] The status of the wxwidgets IPC development

2017-02-13 Thread Alan W. Irwin
On 2017-02-12 22:51-0800 Alan W. Irwin wrote: > I plan to stick with my local instance approach for now (automatically > constructing a PLTwoSemaphore instance and destroying it again for > each call to my transmitBytes and receiveBytes methods), but move to > the private object approach for effic