Re: problems with optimset option name completion in 3.8.0

[John W. Eaton]

On 01/06/2014 01:31 PM, Olaf Till wrote:
> On Fri, Jan 03, 2014 at 11:34:46PM +0100, Olaf Till wrote:
> > ...
> > 1) consider it illegitimate to have option names whose first
> >     characters are equal to a different full option name (means I have
> >     to change the option names in the said functions of the optim
> >     package!),
> >
> > 2) change optimset so that it always matches an option name if it is
> >     given in full, even if there is a longer option name which starts
> >     with the same characters,
> >
> > 3) drop option name completion in optimset.
> > ...
>
> No response means I have to go ahead with 1).

Sorry for not replying earlier.

I would prefer to not have the abbreviated keyword matching feature, but 
I think we have to keep it because Matlab users expect it to work that 
way.  And in case you haven't been looking at the bug tracker lately, we 
get bug reports for all sorts of trivial differences, so I expect we 
would get a report if we disabled matching of abbreviated names in 
optimset.  I assume that Matlab doesn't have any sets of options that 
have the "foo" vs. "foolonger" problem?

jwe