[Octave-bug-tracker] [bug #29942] concatenating with an empty scalar gives an error

[Jaroslav Hajek]

Follow-up Comment #15, bug #29942 (project octave):

Thanks. This shows that cat() really behaves differently from
horzcat/vertcat, who are exact equivalents of [,] and [;]. I more or less
expected this. It means this will require some more significant modifications
from us (now we have horzcat/vertcat simply calling cat(1, ) or cat(2, )).
For cat(), the rule is simple: first try an exact match, and, if it fails,
and if one of operands is 0x0, use the other one, otherwise fail.
Note that this means that cat(3,[],[]) is 0x0x2 (i.e. exact match is
preferred).
I'm still wondering what to do with things like
[zeros(1,0), zeros(0,1)] which produce a 0x0 array. I consider it unwise to
replicate those cases that produce an obsolescence warning. Unfortunately, the
test function I sent to you doesn't catch warnings. I've attached a new one;
can you please redo the same test with it, and again send the results to me?



(file #20701)
    _______________________________________________________

Additional Item Attachment:

File name: test_cat.m                     Size:0 KB


    _______________________________________________________

Reply to this item at:

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

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