See attachment

---

Math Complex.sm (39,03 KiB) scaricato 1468 volta(e).

I do not know if this missing brackets is connected to the behavior already mentioned many times by me. It still remained unsolved. Look at video please. Again, the brackets are missing in the display.

Brackets problem and range()

By looking at the actual commands, I do not know if there is something that could be done

c: range(1,10)*'m

g: (range(1,10))*'m

In the case of comple numbers, the brackets just disappear when inserting another unit

Brackets disappear in complex

z: (5+6*i)*'m

z=(5+6*i)*'m

z=500+600*i@'cm

z=500+600*i@'cm

Regards,
Radovan

Symbolic evaluation seems to work. Although brackets should be kept in all cases.

---

The problem seems to apply to any operator representation of internal functions, if that operator has no bracketing visual structure (i.e. has placeholders without wrapping structure). Internally, complex numbers, ranges, sums and the like, are represented by a function or object which does not require brackets around it.
However, the cartesian representation for complex number is Re + Im i, that is + operation, as well as in sums. In ranges, the internal operator is just side by side putting of numbers, with undefined precedence perhaps somewhere below multiply.

---

Wrote

Symbolic evaluation seems to work.

That was just by chance. The problem persists for symbolic optimization as well.

---

Mhhh.. I don't understand what is the problem about units and imaginary numbers...

What's the expected result?

---

The problem is that the visual representation suggests that P is a sum of dimensionless number 300 and dimensioned imaginary 100*I centimeters (i.e. unitless number is added to a length). Surely, this is only a visual artifact, and internally the program keeps record that the unit (cm) is applied to the whole number (300+100*i), but this is yet another place where the visual representation is plain wrong.

Wrote

The problem is that the visual representation suggests that P is a sum of dimensionless number 300 and dimensioned imaginary 100*I centimeters (i.e. unitless number is added to a length). Surely, this is only a visual artifact, and internally the program keeps record that the unit (cm) is applied to the whole number (300+100*i), but this is yet another place where the visual representation is plain wrong.

Thank you, now I understand the point