|Subject:||Re: Depreciated Functions|
|Date:||Fri, 09 Sep 2005 10:49:22 -0500|
|User-agent:||Mozilla Thunderbird 1.0.6-1.1.fc4 (X11/20050720)|
Paul Kienzle wrote:
I would like octave-forge to be cruft free for the 3.0 release, so it should depend on functions and syntax in 2.9.x.There is a lot of cruft in the C++ functions for supporting older versions of octave. Basically anything in #if is suspicious.
There was a discussion a while back on the Octave-forge list about branching Octave forge so that the main CVS could follow 2.9.x and prepare for 3.0. I have only a minimum knowledge of using CVS--has this been done, or how does one go about doing it? If some of us were to begin making 2.9.x changes could someone go back and branch from an older release? As far as I'm concerned, octave-forge is functional enough on 2.1.71--I suggest we move ahead and only make bug fixes for 2.1.x if something critical comes up.
|[Prev in Thread]||Current Thread||[Next in Thread]|