Separate dispstrs, reprstrs, and mat2str

[apjanke]

I think I got the API design wrong for dispstr. Currently, it defines a single dispstr()/dispstrs() conversion technique. But there are different contexts where a different type of representation is appropriate.

I think it should actually have 3 different representation levels/styles:

• dispstr/dispstrs – Human-readable presentation of the meaning or appearance of the data, targeted toward end users and UIs.
• reprstr/reprstrs – Human-readable presentation of the internal representation, value, or storage format, targeted toward developers and debugging tools.
• mat2str – Matlab-readable conversion of the array to an M-code expression that, when evaled, reproduces the input value.

The dispstr vs reprstr distinction is very much like the distinction Python makes between str and repr.

This realization was informed by my work on Fancyclip.