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

[Alan W. I. <ir...@be...>]

On 2017-02-13 20:24-0000 p.d...@gm... 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 the compiler has the ability
to totally optimise away your classes anyway if it sees fit.

Hi Phil:

I completely agree with you on the perils of premature optimization,
and it sounds like for both of us, if it is a choice between code
clarity and some minor efficiency issue, code clarity wins every time.

> My concern is more style and maintenance related. Placing all the
communication code in one class or a family of parent and child
classes makes sense logically which makes maintenance easier and
allows different communication methods to be swapped in should we need
in the future – for example it would mean that the change from the
current ipc method to a new one would be a single line of code, once
that new method is written.

Good point which I finally understand now.  And it sounds from what
you have said that my mental model of what needs to be done to convert
my present local instance method to the private object method is
correct so I will just go ahead and make that implementation change
without bothering with testing the efficiency of the local instance
versus private object methods.

Thanks very much for the above instructive feedback!

Now that this issue has been cleared up, I hope to have some useful
results to report soon.

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
__________________________