On Wed, Mar 10, 2010 at 08:28:13PM -0800, Søren Hauberg wrote: > No thoughts on this? > > Søren > > tor, 25 02 2010 kl. 22:07 -0800, skrev Søren Hauberg: > > Hi All > > > > I tried to have a look at removing the scripts from the 'optim' package > > and integrate them with the functions using %!demo and %!test blocks. I > > was, however, not able to make the scripts run in the development > > version of Octave as lists has been completely removed (they have been > > deprecated for years). It seems the 'optim' package uses lists quite a > > bit. > > > > The general solution is to replace lists with cell arrays. I can just > > replace all lists by cell arrays, but I guess this will lead to API > > changes in the functions. My question is now: should we do other API > > changes at the same time?
Do you mean other API changes in the affected functions or in other functions also? This touches the question of whether we should have common interfaces for the nonlinear optimization functions, as Matlab has with 'lsqnonlin' and 'lsqcurvefit'. They could be implemented as wrappers. I think common interfaces are reasonable, but possibly copying those of Matlab is not ideal. This would require much thinking, however ... Olaf ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Octave-dev mailing list Octave-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/octave-dev
