[Top][All Lists]

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

[Octave-bug-tracker] [bug #49143] inputdlg processes 2 element row vecto

From: Nicholas Jankowski
Subject: [Octave-bug-tracker] [bug #49143] inputdlg processes 2 element row vector rowscols input as heights instead of height and width
Date: Thu, 15 Sep 2022 11:04:07 -0400 (EDT)

Update of bug #49143 (project octave):

                Severity:              3 - Normal => 2 - Minor              
                Priority:              5 - Normal => 3 - Low                
                  Status:               Confirmed => Postponed              


Follow-up Comment #15:

glad to hear it, Faith. 

Looking at it a bit more, this situation sits at the intersection of two
different handling methods. A 1xm row vector is clearly handled for any m all
the way down to 1, _except_ for m=2 , where it collides with the different
behavior for the nx2 array method, which very clearly handles all values of n
down to 1.  At that point they look identical, one should error if a count
mismatch occurs, the other doesn't.  My guess is Matlab's decision to default
to array behavior is an accidental artifact of their decision tree ordering
rather than a deliberate choice, somewhat supported by the conflicting
documentation which probably appeared sometime after they grafted 'or row
vector' onto the column vector method. 

I was thinking of patching this for compatibility, but I did submit a
mathworks bug and for now I think it's best just to let this sit and see if
anything comes out on either side of that. better than implementing a fix only
for them to decide to change the other way.


Reply to this item at:


Message sent via Savannah

reply via email to

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