[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 3.2 status report
From: |
John W. Eaton |
Subject: |
Re: 3.2 status report |
Date: |
Tue, 05 Aug 2008 22:26:40 -0400 |
On 30-Jul-2008, Jaroslav Hajek wrote:
| I intend to handle this as part of the project to implement Matlab-compatible
| fzero, fminbnd, fsolve and lsqnonlin:
|
http://www.nabble.com/List-of-most-highly-used-matlab-functions.-to18693110.html
OK.
Some code that I help to support uses fsolve fairly extensively and
for various reasons needs to also run properly with the other leading
brand. I don't need 100% compatibility, just enough so that the code
I have can work without change in that other program too. I think all
I really need is for Octave's fsolve to handle an options argument
(the struct returned by optimset) and, as much as possible, to return
compatible INFO values. So those are probably the only changes I will
make. Unfortunately, these changes may break some existing Octave
code, but I think compatibility is more important in this case.
jwe
- Re: 3.2 status report,
John W. Eaton <=