[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #37650] the `inputParser' function is not yet

From: Carnë Draug
Subject: [Octave-bug-tracker] [bug #37650] the `inputParser' function is not yet implemented
Date: Tue, 07 Jan 2014 12:21:48 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20131030 Firefox/17.0 Iceweasel/17.0.10

Follow-up Comment #17, bug #37650 (project octave):

We already have an almost compatible inputParser, why change it for another
almost compatible version? I agree that with your changes, the almost
compatible is bigger but let's consider that we apply them.

We apply your changes now and make a new release of the general package. We
have to tell the current users of inputParser that we changed the API, and
they *must* replace the current workaround with another one. Then, in a couple
of months once Octave 4.2 is released with classdef, we fix inputParser so
it's properly compatible. We have to tell all of them again to remove that

I guess that when we do it the second time, we can simply issue a warning that
the the dispose method is deprecated, no big problem. But the worse part is
that until the proper inputParser gets released in 4.2, we will have no way to
find if dispose() is being called. We can document it now but what about the
code that has already been written? I know that some Octave Forge functions
already use.

I don't think it's worth the bother or risk. There's not many people crying
out for inputParser, so I'd prefer to release a safe version once we get the
possibility, i.e., for the version with classdef which has already been merged
into the default branch.


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]