[Top][All Lists]

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

[Octave-bug-tracker] [bug #55241] movmax should call movfun instead of m

From: A.R. Burgers
Subject: [Octave-bug-tracker] [bug #55241] movmax should call movfun instead of movmax
Date: Wed, 19 Dec 2018 04:00:11 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299


                 Summary: movmax should call movfun instead of movmax
                 Project: GNU Octave
            Submitted by: arb
            Submitted on: Wed 19 Dec 2018 09:00:09 AM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any



movmax(rand(10,1), 3) errors out:

octave:3> movmax(rand(10,1),3)
error: movmax: invalid input at position 1
error: called from                        
    __parse_movargs__ at line 54 column 7 
    movmax at line 130 column 5           
stopped in ../octave/scripts/signal/__parse_movargs__.m at line 54

guess movmax should call movfun instead of itself? With that it change it

diff -r 01f1e70c80b6 scripts/statistics/movmax.m
--- a/scripts/statistics/movmax.m       Tue Dec 18 22:24:37 2018 -0800
+++ b/scripts/statistics/movmax.m       Wed Dec 19 09:53:03 2018 +0100
@@ -127,7 +127,7 @@
     print_usage ();

-  y = movmax (@max, x, wlen, __parse_movargs__ ("movmax", varargin{:}){:});
+  y = movfun (@max, x, wlen, __parse_movargs__ ("movmax", varargin{:}){:});



Reply to this item at:


  Message sent via Savannah

reply via email to

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