Re: [Plplot-devel] Our next release

2014-10-16 Thread Alan W. Irwin
On 2014-10-16 10:59-0700 Alan W. Irwin wrote: > Thanks for that C++ propagation. You have inspired me to take > responsibility (unless you tell me you have already started it) for > the propagation of example 8 and 19 C changes for our swig-generated > language bindings (Java, Python, Lua, and Oc

Re: [Plplot-devel] Our next release

2014-10-16 Thread Alan W. Irwin
On 2014-10-16 14:20+0100 Andrew Ross wrote: > [A release] sounds like a good idea. There have been a number of useful > improvements / fixes since [February]. I agree a release fairly soon is a good idea because I don't want to disappoint anyone whose work remains unreleased because there has be

Re: [Plplot-devel] Why is the set_stream() call commented out for plstream::fill, etc.

2014-10-16 Thread Alan W. Irwin
On 2014-10-16 20:39+0100 Andrew Ross wrote: > > Alan, > > It's because these three functions are callback functions which are > called from another plplot function. They do not operate directly on > a stream. Hi Andrew: I may be misinterpreting what you are saying above, but I noticed many direc

Re: [Plplot-devel] Why is the set_stream() call commented out for plstream::fill, etc.

2014-10-16 Thread Andrew Ross
Alan, It's because these three functions are callback functions which are called from another plplot function. They do not operate directly on a stream. The C++ class maintains a stream variable for each instance of the PLStream class. This means you can have multiple streams (i.e. windows /

Re: [Plplot-devel] Problem(s) with MSYS

2014-10-16 Thread Alan W. Irwin
On 2014-10-16 08:41- Arjen Markus wrote: > [...]You provide enough details so that I can reproduce your steps. Hopefully > I can do that this weekend. Hi Arjen: Since it appears the regression is not due to CMake or PLplot version changes since the last comprehensive MinGW/MSYS tests were d

Re: [Plplot-devel] Our next release

2014-10-16 Thread Alan W. Irwin
On 2014-10-16 14:20+0100 Andrew Ross wrote: > > Alan, > > That sounds like a good idea. There have been a number of useful > improvements / fixes since then. We definitely want to try and > get the various language bindings and examples back into sync > before then. I've now done the C++ examples

[Plplot-devel] Why is the set_stream() call commented out for plstream::fill, etc.

2014-10-16 Thread Alan W. Irwin
Hi Andrew: I just noticed that the set_stream() call was commented out in bindings/c++/plstream.cc for plstream::fill, plstream::fill3, and plstream::gradient while it appears in all (as far as I can tell) other calls. Why are those 3 functions exceptions, or is this a minor bug that has progated

Re: [Plplot-devel] Our next release

2014-10-16 Thread Andrew Ross
Alan, That sounds like a good idea. There have been a number of useful improvements / fixes since then. We definitely want to try and get the various language bindings and examples back into sync before then. I've now done the C++ examples to get the process started. Andrew On Tue, Oct 14, 2

Re: [Plplot-devel] Problem(s) with MSYS

2014-10-16 Thread Arjen Markus
Hi Alan, You provide enough details so that I can reproduce your steps. Hopefully I can do that this weekend. Regards, Arjen > -Original Message- > From: Alan W. Irwin [mailto:[email protected]] > Sent: Thursday, October 16, 2014 10:39 AM > To: Arjen Markus > Cc: PLp

Re: [Plplot-devel] Problem(s) with MSYS

2014-10-16 Thread Alan W. Irwin
> On 2014-10-15 10:28- Arjen Markus wrote: > >> Hi everyone, >> >> I am trying to test the build under MinGW/MSYS, but I have run into a >> problem with the device drivers: >> The example programs can not find them, unless I set PLPLOT_DRV_DIR to the >> directory containing the .driver_info f

Re: [Plplot-devel] Fortran 95 changes in progress

2014-10-16 Thread Alan W. Irwin
On 2014-10-16 06:44- Arjen Markus wrote: > Hi Alan, > I like that idea of providing a dual set of interfaces [for single/double floating point precision for Fortran independent of C core floating precision] very much :). Excellent. > Yes, I will take that responsibility. The details may ne