Hmm, the fact that we don't auto-convert a 1x1 matrix to scalar in
your second case, but we do when the matrix figures as an argument to
defbundle() / _() seems like a nasty inconsistency. In git I've
cancelled that conversion. I think this should be "safer", in that
there are probably more contexts where a scalar can't do the job of a
matrix than vice versa (even though we've tried to minimize such
discrepancies). But we need to watch out for any unwanted side
effects.

Thanks, Allin. Actually I encountered another scenario where this change is welcome: In the context of the bcheck() function, when you give as one member of "target" a 1x1-matrix as a default value, which then apparently is auto-converted to a scalar, and then bcheck() complains that the user input is a vector and thus allegedly of the wrong type.

cheers

sven