Menu
▾
▴
gnuplot-beta
|
From: Allin C. <cot...@wf...> - 2014-06-29 19:44:38
|
I understand that 5.0 is supposed to be the release where the gnuplot developers are free to make some backward-incompatible changes. I've no problem with that, but I wonder if there's any thought to produce a gnuplot 4.8? I get the impression -- admittedly, without studying the code base in detail -- that CVS gnuplot has accumulated a number of helpful fixes along with some nice new options. My notion of a possible 4.8 is basically 5.0 with the backward-incompatible elements reverted. I guess it would be trivial to revert some things (the default color scheme, the default for text in respect of enhanced versus non-enhanced) but maybe less trivial to revert others. Anyway, just wondering. The "use case" is that some of us who employ gnuplot as ancillary to data-analysis software would find it very nice to have a version that's both backward-compatible -- the important thing here is that scripts designed for 4.4 and 4.6 will still work -- and up-to-date with all bug-fixes, and buildable for win64 out of the box. -- Allin Cottrell Department of Economics Wake Forest University |
|
From: sfeam <sf...@us...> - 2014-06-29 20:20:12
|
On Sunday, June 29, 2014 03:44:23 PM Allin Cottrell wrote: > I understand that 5.0 is supposed to be the release where the > gnuplot developers are free to make some backward-incompatible > changes. I've no problem with that, but I wonder if there's any > thought to produce a gnuplot 4.8? The 4.6 development source is a separate branch in CVS. The 4.7 (later 5.0) branch split off from it and gradually diverged. Most bugfixes have been applied to both branches, but they have diverged enough that in some cases the "fix" for a problem in 4.6 is limited to the existence of a better implementation in 5.0. There will be at least one more patchlevel release 4.6.6. My crystal ball does not tell me at what rate fixable bugs will continue to be reported againt 4.6 as opposed to 5.0. Other incremental releases could eventually appear, but I don't see a good rationale for starting a 4.8 series. If a fix/change is compatible then it could go into 4.6; if not then it belongs in 5.0. A brief listing of changes accumulated since the last release is kept at the top of the NEWS files: NEWS New features, changes and fixes in gnuplot version 4.6.6 ======================================================== * NEW linetype keyword "nodraw" can be used to draw only the points in "with lp" * NEW plot option to "skip N" lines at start of an ascii data file * NEW 'set fit prescale' normalized fit parameters before M-L refinement * NEW update svg terminal to grey out the key entry when a plot is toggled off * CHANGE Accept "with image pixels" as a synonym for "with image failsafe" * CHANGE return NaN if a requested numerical data value fins a string instead * CHANGE Consume only one space following the font name in an enhanced test string * FIX Faster recovery from outboard server gnuplot_qt being killed * FIX get rid of O(N^2) memory allocation for string data in long input lines * FIX large integers in iteration spec could cause overflow end condition check * FIX object fillcolors should be consistent with the color of current linetypes * FIX LFS support on 64bit platforms (not backported for 32bit platforms) * FIX timecolumn() applied to non-axis data reports an error rather than faulting * FIX clipping could fail on integer overflow * FIX segfault resulting from strcol(N) applied to empty field in a *.csv file * FIX adjustment of key size to accommodate long key title * FIX treat data value read as "NaN" the same as we would "1/0" * FIX handling of events triggered by closing the qt plot window * FIX iteration failure due to integer overflow * FIX clip r axis tics to current plot boundary * FIX logscale cb axis with volatile data Ethan > I get the impression -- admittedly, without studying the code base > in detail -- that CVS gnuplot has accumulated a number of helpful > fixes along with some nice new options. My notion of a possible 4.8 > is basically 5.0 with the backward-incompatible elements reverted. I > guess it would be trivial to revert some things (the default color > scheme, the default for text in respect of enhanced versus > non-enhanced) but maybe less trivial to revert others. > Anyway, just wondering. The "use case" is that some of us who employ > gnuplot as ancillary to data-analysis software would find it very > nice to have a version that's both backward-compatible -- the > important thing here is that scripts designed for 4.4 and 4.6 will > still work -- and up-to-date with all bug-fixes, and buildable for > win64 out of the box. |
|
From: Tatsuro M. <tma...@ya...> - 2014-06-30 09:10:35
|
----- Original Message ----- > From: sfeam > To: gnuplot-beta > Cc: Allin Cottrell > Date: 2014/6/30, Mon 05:16 > Subject: Re: gnuplot 4.8? > > On Sunday, June 29, 2014 03:44:23 PM Allin Cottrell wrote: >> I understand that 5.0 is supposed to be the release where the >> gnuplot developers are free to make some backward-incompatible >> changes. I've no problem with that, but I wonder if there's any >> thought to produce a gnuplot 4.8? > > The 4.6 development source is a separate branch in CVS. > The 4.7 (later 5.0) branch split off from it and gradually diverged. > Most bugfixes have been applied to both branches, but they have > diverged enough that in some cases the "fix" for a problem in 4.6 > is limited to the existence of a better implementation in 5.0. > > There will be at least one more patchlevel release 4.6.6. > My crystal ball does not tell me at what rate fixable bugs will continue > to be reported againt 4.6 as opposed to 5.0. Other incremental > releases could eventually appear, but I don't see a good rationale for > starting a 4.8 series. If a fix/change is compatible then it could go into > 4.6; if not then it belongs in 5.0. > > A brief listing of changes accumulated since the last release is > kept at the top of the NEWS files: > > NEWS > New features, changes and fixes in gnuplot version 4.6.6 > ======================================================== > > * NEW linetype keyword "nodraw" can be used to draw only the points in > "with lp" > * NEW plot option to "skip N" lines at start of an ascii data file > * NEW 'set fit prescale' normalized fit parameters before M-L refinement > * NEW update svg terminal to grey out the key entry when a plot is toggled off > * CHANGE Accept "with image pixels" as a synonym for "with image > failsafe" > * CHANGE return NaN if a requested numerical data value fins a string instead > * CHANGE Consume only one space following the font name in an enhanced test > string > * FIX Faster recovery from outboard server gnuplot_qt being killed > * FIX get rid of O(N^2) memory allocation for string data in long input lines > * FIX large integers in iteration spec could cause overflow end condition check > * FIX object fillcolors should be consistent with the color of current linetypes > * FIX LFS support on 64bit platforms (not backported for 32bit platforms) > * FIX timecolumn() applied to non-axis data reports an error rather than > faulting > * FIX clipping could fail on integer overflow > * FIX segfault resulting from strcol(N) applied to empty field in a *.csv file > * FIX adjustment of key size to accommodate long key title > * FIX treat data value read as "NaN" the same as we would > "1/0" > * FIX handling of events triggered by closing the qt plot window > * FIX iteration failure due to integer overflow > * FIX clip r axis tics to current plot boundary > * FIX logscale cb axis with volatile data > > Ethan Do you really make package of gnuplot-4.6.6? If it will be upload on the web, I can prepare windows and Cygwin binaries both for 32 and 64 bit. Tatsuro |
|
From: sfeam <sf...@us...> - 2014-06-30 14:28:18
|
On Monday, June 30, 2014 06:10:24 PM Tatsuro MATSUOKA wrote: > ----- Original Message ----- > > > From: sfeam > > To: gnuplot-beta > > Cc: Allin Cottrell > > Date: 2014/6/30, Mon 05:16 > > Subject: Re: gnuplot 4.8? > > > > On Sunday, June 29, 2014 03:44:23 PM Allin Cottrell wrote: > >> I understand that 5.0 is supposed to be the release where the > >> gnuplot developers are free to make some backward-incompatible > >> changes. I've no problem with that, but I wonder if there's any > >> thought to produce a gnuplot 4.8? > > > > The 4.6 development source is a separate branch in CVS. > > The 4.7 (later 5.0) branch split off from it and gradually diverged. > > Most bugfixes have been applied to both branches, but they have > > diverged enough that in some cases the "fix" for a problem in 4.6 > > is limited to the existence of a better implementation in 5.0. > > > > There will be at least one more patchlevel release 4.6.6. > > My crystal ball does not tell me at what rate fixable bugs will continue > > to be reported againt 4.6 as opposed to 5.0. Other incremental > > releases could eventually appear, but I don't see a good rationale for > > starting a 4.8 series. If a fix/change is compatible then it could go > > into 4.6; if not then it belongs in 5.0. > > > > A brief listing of changes accumulated since the last release is > > kept at the top of the NEWS files: > > > > NEWS > > New features, changes and fixes in gnuplot version 4.6.6 > > ======================================================== > > > > * NEW linetype keyword "nodraw" can be used to draw only the points in > > "with lp" > > * NEW plot option to "skip N" lines at start of an ascii data file > > * NEW 'set fit prescale' normalized fit parameters before M-L refinement > > * NEW update svg terminal to grey out the key entry when a plot is toggled > > off * CHANGE Accept "with image pixels" as a synonym for "with image > > failsafe" > > * CHANGE return NaN if a requested numerical data value fins a string > > instead * CHANGE Consume only one space following the font name in an > > enhanced test string > > * FIX Faster recovery from outboard server gnuplot_qt being killed > > * FIX get rid of O(N^2) memory allocation for string data in long input > > lines * FIX large integers in iteration spec could cause overflow end > > condition check * FIX object fillcolors should be consistent with the > > color of current linetypes * FIX LFS support on 64bit platforms (not > > backported for 32bit platforms) * FIX timecolumn() applied to non-axis > > data reports an error rather than faulting > > * FIX clipping could fail on integer overflow > > * FIX segfault resulting from strcol(N) applied to empty field in a *.csv > > file * FIX adjustment of key size to accommodate long key title > > * FIX treat data value read as "NaN" the same as we would > > "1/0" > > * FIX handling of events triggered by closing the qt plot window > > * FIX iteration failure due to integer overflow > > * FIX clip r axis tics to current plot boundary > > * FIX logscale cb axis with volatile data > > > > Ethan > > Do you really make package of gnuplot-4.6.6? > If it will be upload on the web, I can prepare windows and Cygwin binaries > both for 32 and 64 bit. I have shown the NEWS file from the 4.6 CVS repository. Each PATCHLEVEL release is basically a snapshot of the repository. 4.6.5 was a snapshot from February 2014. Some time later this year we will take another snapshot and this will be release 4.6.6. It will contain the changes listed above and any other changes made between now and the tie of release. Ethan > Tatsuro |
|
From: Tatsuro M. <tma...@ya...> - 2014-06-30 19:21:45
|
----- Original Message ----- > From: sfeam > To: Tatsuro MATSUOKA > Cc: gnuplot-beta Allin Cottrell > Date: 2014/6/30, Mon 23:25 > Subject: Re: gnuplot 4.8? > > On Monday, June 30, 2014 06:10:24 PM Tatsuro MATSUOKA wrote: >> ----- Original Message ----- >> >> > From: sfeam >> > To: gnuplot-beta >> > Cc: Allin Cottrell >> > Date: 2014/6/30, Mon 05:16 >> > Subject: Re: gnuplot 4.8? >> > >> > On Sunday, June 29, 2014 03:44:23 PM Allin Cottrell wrote: >> >> I understand that 5.0 is supposed to be the release where the >> >> gnuplot developers are free to make some backward-incompatible >> >> changes. I've no problem with that, but I wonder if > there's any >> >> thought to produce a gnuplot 4.8? >> > >> > The 4.6 development source is a separate branch in CVS. >> > The 4.7 (later 5.0) branch split off from it and gradually diverged. >> > Most bugfixes have been applied to both branches, but they have >> > diverged enough that in some cases the "fix" for a problem > in 4.6 >> > is limited to the existence of a better implementation in 5.0. >> > >> > There will be at least one more patchlevel release 4.6.6. >> > My crystal ball does not tell me at what rate fixable bugs will > continue >> > to be reported againt 4.6 as opposed to 5.0. Other incremental >> > releases could eventually appear, but I don't see a good rationale > for >> > starting a 4.8 series. If a fix/change is compatible then it could > go >> > into 4.6; if not then it belongs in 5.0. >> > >> > A brief listing of changes accumulated since the last release is >> > kept at the top of the NEWS files: >> > >> > NEWS >> > New features, changes and fixes in gnuplot version 4.6.6 >> > ======================================================== >> > >> > * NEW linetype keyword "nodraw" can be used to draw only the > points in >> > "with lp" >> > * NEW plot option to "skip N" lines at start of an ascii > data file >> > * NEW 'set fit prescale' normalized fit parameters before M-L > refinement >> > * NEW update svg terminal to grey out the key entry when a plot is > toggled >> > off * CHANGE Accept "with image pixels" as a synonym for > "with image >> > failsafe" >> > * CHANGE return NaN if a requested numerical data value fins a string >> > instead * CHANGE Consume only one space following the font name in an >> > enhanced test string >> > * FIX Faster recovery from outboard server gnuplot_qt being killed >> > * FIX get rid of O(N^2) memory allocation for string data in long > input >> > lines * FIX large integers in iteration spec could cause overflow end >> > condition check * FIX object fillcolors should be consistent with the >> > color of current linetypes * FIX LFS support on 64bit platforms (not >> > backported for 32bit platforms) * FIX timecolumn() applied to non-axis >> > data reports an error rather than faulting >> > * FIX clipping could fail on integer overflow >> > * FIX segfault resulting from strcol(N) applied to empty field in a > *.csv >> > file * FIX adjustment of key size to accommodate long key title >> > * FIX treat data value read as "NaN" the same as we would >> > "1/0" >> > * FIX handling of events triggered by closing the qt plot window >> > * FIX iteration failure due to integer overflow >> > * FIX clip r axis tics to current plot boundary >> > * FIX logscale cb axis with volatile data >> > >> > Ethan >> >> Do you really make package of gnuplot-4.6.6? >> If it will be upload on the web, I can prepare windows and Cygwin binaries >> both for 32 and 64 bit. > > I have shown the NEWS file from the 4.6 CVS repository. > Each PATCHLEVEL release is basically a snapshot of the repository. > 4.6.5 was a snapshot from February 2014. > Some time later this year we will take another snapshot and this will > be release 4.6.6. It will contain the changes listed above and any > other changes made between now and the tie of release. > > Ethan OK.Thanks! Tatsuro |
|
From: Tatsuro M. <tma...@ya...> - 2014-07-01 04:39:27
|
----- Original Message ----- > From: Tatsuro MATSUOKA > To: Merritt Ethan > Cc: gnuplot-beta Allin Cottrell > Date: 2014/7/1, Tue 04:21 > Subject: Re: gnuplot 4.8? > > > > > > ----- Original Message ----- >> From: sfeam >> To: Tatsuro MATSUOKA >> Cc: gnuplot-beta Allin Cottrell >> Date: 2014/6/30, Mon 23:25 >> Subject: Re: gnuplot 4.8? >> >> On Monday, June 30, 2014 06:10:24 PM Tatsuro MATSUOKA wrote: >>> ----- Original Message ----- >>> >>> > From: sfeam >>> > To: gnuplot-beta >>> > Cc: Allin Cottrell >>> > Date: 2014/6/30, Mon 05:16 >>> > Subject: Re: gnuplot 4.8? >>> > >>> > On Sunday, June 29, 2014 03:44:23 PM Allin Cottrell wrote: >>> >> I understand that 5.0 is supposed to be the release where > the >>> >> gnuplot developers are free to make some > backward-incompatible >>> >> changes. I've no problem with that, but I wonder if >> there's any >>> >> thought to produce a gnuplot 4.8? >>> > >>> > The 4.6 development source is a separate branch in CVS. >>> > The 4.7 (later 5.0) branch split off from it and gradually > diverged. >>> > Most bugfixes have been applied to both branches, but they have >>> > diverged enough that in some cases the "fix" for a > problem >> in 4.6 >>> > is limited to the existence of a better implementation in 5.0. >>> > >>> > There will be at least one more patchlevel release 4.6.6. >>> > My crystal ball does not tell me at what rate fixable bugs will >> continue >>> > to be reported againt 4.6 as opposed to 5.0. Other incremental >>> > releases could eventually appear, but I don't see a good > rationale >> for >>> > starting a 4.8 series. If a fix/change is compatible then it > could >> go >>> > into 4.6; if not then it belongs in 5.0. >>> > >>> > A brief listing of changes accumulated since the last release is >>> > kept at the top of the NEWS files: >>> > >>> > NEWS >>> > New features, changes and fixes in gnuplot version 4.6.6 >>> > ======================================================== >>> > >>> > * NEW linetype keyword "nodraw" can be used to draw > only the >> points in >>> > "with lp" >>> > * NEW plot option to "skip N" lines at start of an > ascii >> data file >>> > * NEW 'set fit prescale' normalized fit parameters before > M-L >> refinement >>> > * NEW update svg terminal to grey out the key entry when a plot > is >> toggled >>> > off * CHANGE Accept "with image pixels" as a synonym > for >> "with image >>> > failsafe" >>> > * CHANGE return NaN if a requested numerical data value fins a > string >>> > instead * CHANGE Consume only one space following the font name > in an >>> > enhanced test string >>> > * FIX Faster recovery from outboard server gnuplot_qt being > killed >>> > * FIX get rid of O(N^2) memory allocation for string data in long > >> input >>> > lines * FIX large integers in iteration spec could cause overflow > end >>> > condition check * FIX object fillcolors should be consistent with > the >>> > color of current linetypes * FIX LFS support on 64bit platforms > (not >>> > backported for 32bit platforms) * FIX timecolumn() applied to > non-axis >>> > data reports an error rather than faulting >>> > * FIX clipping could fail on integer overflow >>> > * FIX segfault resulting from strcol(N) applied to empty field in > a >> *.csv >>> > file * FIX adjustment of key size to accommodate long key title >>> > * FIX treat data value read as "NaN" the same as we > would >>> > "1/0" >>> > * FIX handling of events triggered by closing the qt plot window >>> > * FIX iteration failure due to integer overflow >>> > * FIX clip r axis tics to current plot boundary >>> > * FIX logscale cb axis with volatile data >>> > >>> > Ethan >>> >>> Do you really make package of gnuplot-4.6.6? >>> If it will be upload on the web, I can prepare windows and Cygwin > binaries >>> both for 32 and 64 bit. >> >> I have shown the NEWS file from the 4.6 CVS repository. >> Each PATCHLEVEL release is basically a snapshot of the repository. >> 4.6.5 was a snapshot from February 2014. >> Some time later this year we will take another snapshot and this will >> be release 4.6.6. It will contain the changes listed above and any >> other changes made between now and the tie of release. >> >> Ethan > > > OK.Thanks! > > Tatsuro > I have lost the record or memory how to access stable branch on the cvs repository. I will appreciate if you show me the way Tatsuro |
|
From: Karl R. <ra...@un...> - 2014-07-01 07:59:40
|
Am 01.07.2014 06:39, schrieb Tatsuro MATSUOKA: >> > I have lost the record or memory how to access stable branch on the cvs repository. > I will appreciate if you show me the way > > Tatsuro > export CVSROOT=:pserver:ano...@gn...:/cvsroot/gnuplot cvs login cvs -z3 checkout -r branch-4-6-stable -d gnuplot46 gnuplot This really should be mentioned somewhere on the gnuplot.info homepage. Karl -- Karl-Friedrich Ratzsch (Dipl. Chem.) Freiburger Materialforschungszentrum / Universität Freiburg Stefan-Meier-Straße 21, 79104 Freiburg im Breisgau Tel. 0761/203-4748 Fax:-4701 ra...@un... |
|
From: <pl...@pi...> - 2014-07-01 11:49:18
|
On 07/01/14 10:03, Karl Ratzsch wrote: > > Am 01.07.2014 06:39, schrieb Tatsuro MATSUOKA: > >>> >> I have lost the record or memory how to access stable branch on the cvs repository. >> I will appreciate if you show me the way >> >> Tatsuro >> > > export > CVSROOT=:pserver:ano...@gn...:/cvsroot/gnuplot > cvs login > cvs -z3 checkout -r branch-4-6-stable -d gnuplot46 gnuplot > > This really should be mentioned somewhere on the gnuplot.info homepage. > > Karl > I did point out about a month ago that it was not particularly easy to find cvs instruction. /Peter. |
|
From: Tatsuro M. <tma...@ya...> - 2014-07-01 09:58:57
|
----- Original Message ----- > From: Karl Ratzsch > To: gnuplot-beta > Cc: > Date: 2014/7/1, Tue 17:03 > Subject: Re: gnuplot 4.8? > > Am 01.07.2014 06:39, schrieb Tatsuro MATSUOKA: > >>> >> I have lost the record or memory how to access stable branch on the cvs > repository. >> I will appreciate if you show me the way >> >> Tatsuro >> > > export > CVSROOT=:pserver:ano...@gn...:/cvsroot/gnuplot > cvs login > cvs -z3 checkout -r branch-4-6-stable -d gnuplot46 gnuplot > > This really should be mentioned somewhere on the gnuplot.info homepage. > > Karl Thanks Karl I could check out the branch-4-6-stable source. > This really should be mentioned somewhere on the gnuplot.info homepage. It will be nice to try recent fixed stable source. |
|
From: Tatsuro M. <tma...@ya...> - 2014-07-03 04:41:16
|
----- Original Message ----- > From: Tatsuro MATSUOKA > To: Karl Ratzsch ; gnuplot-beta > Cc: > Date: 2014/7/1, Tue 18:58 > Subject: Re: gnuplot 4.8? > ----- Original Message ----- >> From: Karl Ratzsch >> To: gnuplot-beta >> Cc: >> Date: 2014/7/1, Tue 17:03 >> Subject: Re: gnuplot 4.8? >> >> Am 01.07.2014 06:39, schrieb Tatsuro MATSUOKA: >> >>>> >>> I have lost the record or memory how to access stable branch on the > cvs >> repository. >>> I will appreciate if you show me the way >>> >>> Tatsuro >>> >> >> export >> CVSROOT=:pserver:ano...@gn...:/cvsroot/gnuplot >> cvs login >> cvs -z3 checkout -r branch-4-6-stable -d gnuplot46 gnuplot >> >> This really should be mentioned somewhere on the gnuplot.info homepage. >> >> Karl > > > Thanks Karl > I could check out the branch-4-6-stable source. > >> This really should be mentioned somewhere on the gnuplot.info homepage. > > It will be nice to try recent fixed stable source. > > With the source (latest ChangeLog date 2014-06-30), I could build native windows binaries (32 and 64 bit) ans Cygwin binary (32 bit and 64 bit). For 64 bit build for native windows, the patch by Allin Cottrell is used. (http://gnuplot.10905.n7.nabble.com/gnuplot-on-64-bit-Windows-again-td17580.html attacment file gnuplot-win64.diff) Tatsuro |
