On 1 November 2011 14:05, Olaf Till <olaf.t...@uni-jena.de> wrote:
> On Tue, Nov 01, 2011 at 02:54:17PM +0100, Olaf Till wrote:
>> On Tue, Nov 01, 2011 at 12:40:09PM +0000, Carnė Draug wrote:
>> > On 1 November 2011 10:51, Olaf Till <olaf.t...@uni-jena.de> wrote:
>> > > I would like to remove optimset_compat of package optim, since Octave
>> > > since before version 3.4 has optimset. Also, optimset_compat is not
>> > > used within the optim package, except that it is tested by a
>> > > testscript.
>> > >
>> > > BTW, it would be nice if someone could decide on whether
>> > > fminunc_compat is still needed. fminunc is now also in
>> > > Octave. fminunc_compat does not itself do optimization, but calls
>> > > other functions, which could be called directly. But I don't know if
>> > > using fminunc_compat could still be desirable in some cases.
>> >
>> > Hi,
>> >
>> > I don't know anything about the function, but does it do anything that
>> > octave's fminunc doesn't?
>> >
>> > Carnė
>>
>> I can't easily say. It is obviously there to provide an fminunc-like
>> interface to 'minimize', which itself seems to be a wrapper for
>> several backends. I think fminunc reaches always the same backend, but
>> it would take me much time to be sure with the used system of options.
>>
>> Olaf
>
> And it just occured to me that users of fminunc_compat probably have a
> use for optimset_compat, too, since fminunc_compat does not register
> its options for Octaves optimset ...  Olaf

Why not have those functions issue a warning right after the call?
Something like:
  warning ("'fminunc_compat' has been deprecated in favor of 'fminunc'
which is now part of octave core. This function will be removed from
future versions of the 'optim' package");

Carnë

------------------------------------------------------------------------------
RSA&reg; Conference 2012
Save &#36;700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev

Reply via email to