Re: [OctDev] release goals

[Etienne G. <et...@is...>]

  Hi all

On Thu, Sep 19, 2002 at 11:37:56PM -0400, Paul Kienzle wrote:
# Hi all,
# 
[snip]
# 
# Off the top of my head, struct/*.cc and FIXES/fsolve.cc are broken.  A more
                               ^^
                           In 2.1.37, you mean?

# difficult problem is that lo-sstream.h is missing from the octave installation
# so a lot more things look broken than really are.  I suppose we could
# keep our own copy somewhere (e.g., in FIXES) and use -I$(TOPDIR)/FIXES if
# octave version is 2.1.36.  Or we could just document the problem.
# 
# Unfortunately m-files will also have to change:
# 	* replace ... with varargin/varargout
# 	* replace all_va_args with varargin{:}
# 	* for [v,k]=struct ... end now sets v to a list rather than a value
# 	* anything else?
# 
# We could use version tests in our code.

  ^^ 
  Can that do 'function foo (x,...)' and 'function foo (x,varargin)'

# We could use a preprocessor and set up make to convert file.m.in to file.m.
# We could have file.m-2.1.35 for example for versions up to and including
# 2.1.35 and file.m for later versions.
#
# I'm in favour of using a preprocessor because I'm not very good at fixing

  I prefer the preprocessor option too.
 
[snip] 
# Anything else?

  What about supporting 2.1.36, and the day 2.1.37 comes out, we fix
things (duration : a few weeks) and release a new octave-forge when
it's done. No worries until 2.1.37, none one month after it comes
either. Or am I over-optimistic?


  Cheers,

  Etienne

# Paul Kienzle
# pki...@us...