fre, 12 03 2010 kl. 10:13 +0100, skrev Olaf Till: > To your original question, I'd now think that just the necessary > change should be made (your suggestion of disallowing extra arguments > since we have anonymous functions seems fine to me), and additional > interface changes are not necessary so much since (IMO) there should > be general wrappers anyway sometime. How to implement the latter could > be discussed separately from the original problem.
I've been looking a bit at this. My first thought was simply to remove the option of passing extra arguments to the functions via lists. However, it seems like lists are also used to control which dimensions should be optimised. Lists also seems to be used internally. I don't use the these functionalities, so I fear that if I "fix" the problems, then I'll just break the code. So, I would really appreciate some help here. Can somebody who actually use all this 'list' stuff look into replacing it by something more modern? Let me stress that if this doesn't happen, then 'optim' will NOT be usable with Octave 3.4. IMHO that would be quite a loss. Søren ------------------------------------------------------------------------------ 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
