From: Andrew R. <and...@us...> - 2009-01-20 12:25:30
|
On Mon, Jan 19, 2009 at 11:37:01AM -0800, Alan Irwin wrote: > On 2009-01-19 10:12-0000 Andrew Ross wrote: > > > > > We've said that we will drop support for octave 2.1.x from this release. > > Actually, as stated in README.release we dropped support for 2.1.x in the > 5.9.1 release, but I wanted to leave the notice in for this release and > subsequent ones up to and including our next stable release for those > users who just skip from one stable release to the next or skip some > of the development releases. > > > Are people really happy for me to go and remove the legacy code which is > > in place to support this? This would make life easier and also remove > > some slightly irritating warnings for octave 3.0. Octave 3.0 seems > > pretty stable now and all distributions for the last year or so that I > > have been coming with it. In general I don't like removing backwards > > compatibility, but we have announced that we will do this. > > Go for it. Cruft removal is a good thing to do, and besides the octave > download page doesn't even give directions for downloading 2.1.x any > more. Done. I've also fixed automatic replotting which has always previously been broken with octave 3.0. If octave < 2.9 is installed, then cmake will now disable the bindings. Andrew |