[Plplot-devel] Is it time to remove our old fortran and our old Tcl bindings and examples?

2017-08-28 Thread Alan W. Irwin
Hi Arjen: This e-mail concerns cruft removal for both the Fortran and Tcl cases. Fortran: We introduced the new Fortran binding and corresponding examples as of PLplot-5.12.0 (released on 2017-01-29), but as a safety measure supplied the old Fortran binding and examples if the user specified

[Plplot-devel] Removal of our file support (consisting mostly of test examples in examples/perl) for the external PDL::Graphics::PLplot project?

2017-08-28 Thread Alan W. Irwin
By historical accident Rafael (followed by other developers here) helped out with Doug Hunt's external PDL::Graphics::PLplot project by supplying test examples in examples/perl to see how well that external project's results agreed with our C examples (which was typically not very well). Also

Re: [Plplot-devel] Qt(5) problems

2017-08-28 Thread Alan W. Irwin
On 2017-08-28 15:06+0200 Ole Streicher wrote: [...] since Qt4 is going to be deprecated very soon in Debian [1] [...] [1] https://lists.debian.org/debian-devel-announce/2017/08/msg6.html By the way, thanks very much for that link. I had no idea that upstream Qt4 maintenance had

Re: [Plplot-devel] Qt(5) problems

2017-08-28 Thread Alan W. Irwin
On 2017-08-28 15:06+0200 Ole Streicher wrote: Hi, on my path to get plplot compiled for Debian, I have a number of problems during the execution to the Qt tests. I first was trying to use Qt5, since Qt4 is going to be deprecated very soon in Debian [1], but I see the same problems with Qt4.

[Plplot-devel] Qt(5) problems

2017-08-28 Thread Ole Streicher
Hi, on my path to get plplot compiled for Debian, I have a number of problems during the execution to the Qt tests. I first was trying to use Qt5, since Qt4 is going to be deprecated very soon in Debian [1], but I see the same problems with Qt4. Occasionally, I get now lots messages like Qt:

[Plplot-devel] git blog

2017-08-28 Thread Alan W. Irwin
Can some git guru here advise me what I need to do to publish a bug fix release (in case during this release cycle some bug fix is so urgent that we need to make a bug-fix 5.13.1 release to propagate that fix to our users)? I assume I would branch a private topic branch called "release" for this

[Plplot-devel] Deprecate plshade1?

2017-08-28 Thread Alan W. Irwin
Does anyone have any objections to me deprecating plshade1 for this next release, to be followed up by removing it altogether in the next release? plshade1 differs from plshade only in the type of its first argument (pointer to a contiguous block of memory that contains nx by ny matrix values

Re: [Plplot-devel] On-going Windows testing, and our Wiki summary of it

2017-08-28 Thread Alan W. Irwin
Hi Arjen (off list): There are at least three motivations why I would prefer you to continue a slow but steady pace of testing right now rather than dropping it for a while. 1. Continuing the testing effort you started before the 5.13.0 release should be more efficient than dropping testing

Re: [Plplot-devel] On-going Windows testing, and our Wiki summary of it

2017-08-28 Thread Arjen Markus
Hi Alan, > -Original Message- > From: Alan W. Irwin [mailto:ir...@beluga.phys.uvic.ca] > Sent: Monday, August 28, 2017 10:05 AM > Hi Arjen: > > Could you please take a look at > > where I have recently added a

[Plplot-devel] On-going Windows testing, and our Wiki summary of it

2017-08-28 Thread Alan W. Irwin
On 2017-08-25 23:34-0700 Alan W. Irwin wrote: Arjen: Your comprehensive tests on MinGW-w64/MSYS2, Cygwin, and MSVC (+ Unix tools to help with testing) are really important since they are fundamental to improving our build system for those platforms. Nevertheless, because 5.13.0 was late we