[Octave-bug-tracker] [bug #57199] [octave-forge] (optim) lsqnonlin in version 1.6.0 fails with Octave 6.0

[Philip Nienhuis]

Follow-up Comment #4, bug #57199 (project octave):

@Olaf:
Your reasoning is fair enough.

I usually work with bleeding edge Octave so I have to keep the packages I
maintain (io and mapping) working with dev Octave but that is a personal
thing.

After a brief look it turned out the lsqnonlin.m code is too involved for me -
I rarely if ever use the optim package anyway.
And no, I wouldn't know which change in core Octave can be pointed to.

So I wouldn't mind if you set status to "postponed".


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57199>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/