[Octave-bug-tracker] [bug #61840] Octave gives wrong (misleading) error message

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?61840>

                 Summary: Octave gives wrong (misleading) error message
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Mon 17 Jan 2022 11:49:36 AM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error or Warning
                  Status: None
             Assigned to: None
         Originator Name: Bernhard Schweighofer
        Originator Email: bernhard.schweighofer@tugraz.at
             Open/Closed: Open
                 Release: 6.4.0
         Discussion Lock: Any
        Operating System: GNU/Linux

    _______________________________________________________

Details:

Got the following error message when I tried to execute 'medfilt1' (from the
signal package / octave forge):


error: 'medfilt1' undefined near line 1, column 1

The 'medfilt1' function belongs to the signal package from Octave 
Forge but has not yet been implemented.

Please read <https://www.octave.org/missing.html> to learn how
you can contribute missing functionality.


But, the medfilt1 function is already implemented! I'm using the signal
package version 1.4.1 and it is loaded... So I took a deeper look into the
problem.
Going to the directory where the medfilt1 file is located
(~/octave/signal-1.4.1/x86_64-pc-linux-gnu-api-v55) and again executing
'medfilt1', I got a different error message:


error: API version api-v55 found in .oct file function 'medfilt1'
       does not match the running Octave (API version api-v56)
       this can lead to incorrect results or other failures
       you can fix this problem by recompiling this .oct file


Now this error message does make sense. I reinstalled the signal package (pkg
install -forge signal) which forced a recompile. The
x86_64-pc-linux-gnu-api-v55 subdirectory in the signal-1.4.1 directory changed
(as expected) to ...-v56 and now all works fine.

So in the end, the initial error-message was completely misleading. Maybe
somebody can fix this?

kind regards
Bernhard





    _______________________________________________________

Reply to this item at:

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

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