[Octave-bug-tracker] [bug #47173] mtimes allows non-conformant arguments, looks similar to unexpected broadcasting

[Nicholas Jankowski]

URL:
  <http://savannah.gnu.org/bugs/?47173>

                 Summary: mtimes allows non-conformant arguments, looks
similar to unexpected broadcasting
                 Project: GNU Octave
            Submitted by: nrjank
            Submitted on: Tue 16 Feb 2016 09:19:01 PM GMT
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Nicholas Jankowski
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.0.1-rc1
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

This just came up on the help mailing list. I think the following example
presents the issue concisely:


octave:15> ones(2,3)*ones(3,1)
ans =

   3
   3

octave:16> ones(2,3)*ones(3,1,2)
ans =

   3   3
   3   3

octave:17> ones(2,3)*ones(3,1,2,2)
ans =

   3   3   3   3
   3   3   3   3

octave:18> ones(2,3)*ones(3,1,2,2,2)
ans =

   3   3   3   3   3   3   3   3
   3   3   3   3   3   3   3   3


Each of those except the first should produce a non-conformant argument error.
(Matlab 2015b errors out in these cases)

The email discussion thought maybe the issue had to do with broadcasting, but
it now seems unrelated (and should be, since .* is uninvolved).  

Is mtimes flattening the argument to 2D (from nxm * mxpxq to nxm * mx(p*q) )
and skipping any conformance checking?

(verified still exists in 4.0.1rc3)




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47173>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/