On Fri, 10 Feb 2017, Sven Schreiber wrote:
Am 10.02.2017 um 16:18 schrieb Allin Cottrell:
> For package authors: here's a listing of deprecation warnings produced
> by packages currently on the server. If you can find time to update your
> package(s) that would be much appreciated!
>
> Note that the warning for using '=' as an equality test is very explicit
> so it should be easy to find the location in the code.
The list is much longer than expected...
Seriously, I don't think a message to gretl-devel is enough. We have to use
the email adresses given in the packages, too.
Yes, probably so.
Also, I think we should offer a little more support. A script that
catches
and perhaps even autocorrects the most common occurrences for example. As
Oleh indicated, a "=" in the same line as an "if" for example can
only mean
"==" I think (right?). (... outside of a foreign block, that is....)
The hansl parser knows what cases need fixing, but it doesn't have the
facility to change its input (or at least not so the change will be
saved). Hmm, may be worth investigating though.
> * Use of "catch" on calls to user-defined functions
> (generates a warning, really should be an error by now):
> coint2rec.gfn
OK, this one concerns me myself. What again was the suggested alternative?
Re-write the function to provide an error code?
The "catch" should be moved onto the specific built-in command or
function call that could provoke an error. And responding to this
might involve the user-function providing an error code.
Allin