I agree, so in the absence of any input from Andrew I will go ahead with that 
tomorrow afternoon.

Phil

-----Original Message-----
From: "Alan W. Irwin" <ir...@beluga.phys.uvic.ca>
Sent: ‎22/‎10/‎2014 20:34
To: "Phil Rosenberg" <philip_rosenb...@yahoo.com>
Cc: "Andrew Ross" <andrewr...@users.sourceforge.net>; "PLplot development list" 
<Plplot-devel@lists.sourceforge.net>
Subject: RE: [Plplot-devel] Why is the set_stream() call 
commentedoutforplstream::fill, etc.

On 2014-10-22 19:57+0100 Phil Rosenberg wrote:

> Hi Alan
> I didn't think of that either. It built on my system as I use static builds 
> so the C library gets directly linked anyway.
> Andrew, do you have any preference. Presumably the option b or c from before 
> are required?

My own (somewhat inexpert) opinion is (c) is gross overkill, but (b)
now has the advantage since it doesn't require user's applications and
libraries be linked to both the plplotcxx and plplot libraries. (which
is the requirement for the current (a) option that has been
implemented).

If Andrew is willing to go along with (b), then please go for
distinctive names for those C++ callbacks such as fill_callback and
tr[0-2]_callback.

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
__________________________
------------------------------------------------------------------------------
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to