Var i As Integer = 1 Var col As String = (i + 2).ToString Compiler says: Type mismatch error. Expected String, but got Integer. Xojo 2026r1.2 macOS Sequoia Str(i + 2) works fine.

This works as expected: Var i As Integer = 1 Var col As String = Integer(i + 2).ToString

[image] Christian_Wheel: 1+1.ToString() (1+1).ToString is NOT the same as 1+1.ToString(). The parentheses disambiguate the order of operations. The latter would be bad design.

[image] Christian Wheel: (1+1).ToString is NOT the same as 1+1.ToString(). The parentheses disambiguate [image] Rick_Araujo: you need (1+1) instead 1+1 due to some disambiguations Well, I said that above, even with an example, and you criticized it and called it “bad design”? Now you a…

I think we’re in agreement - I provided some additional examples in other languages but my original statement was, and consistently has been that without the parentheses it’s bad design and I’m glad Xojo doesn’t support it (even WITH the parentheses Xojo doesn’t support it, but that’s not what I’ve …

[image] John Eidsvoog: Var i As Integer = 1 Var col As String = (i + 2).ToString Compiler says: Type mismatch error. Expected String, but got Integer. ? [image] Christian Wheel: I think we’re in agreement Well, my argument was considering the OP question. His point was (expression).m…

Hello, str() has always existed—why should one use .tostring for everything now? var a as string a = str(1+1*2+1.2,“00.00”) messagebox a rem = 04.20

[image] Eric Williams: And yet you can do this: If (A and B) then Apples and oranges. Your IF example does not use an extension method. While one might expect the extension method in the original example to work, Xojo’s compiler simply doesn’t work that way. I’m sure it could be implemented,…

[image] RudolfJ: str() has always existed—why should one use .tostring for everything now? Because str(variable) is API1 and variable.toString is API2.

If you double-check my comment, I was responding to a related assertion by another poster about how Xojo treats expressions encapsulated in parens.

[image] RudolfJ: str() has always existed—why should one use .tostring In OOP (like Xojo) or MP POP (Protocol Oriented like Swift) or MP TBP (multi-paradigm, trait based, like Rust) there’s a common feature called chaining that allows to write short, clear and readable direct expression seque…

[image] Beatrix Willius: Because str(variable) is API1 and variable.toString is API2. As @Lawrence_Johnson pointed out, Str() is not deprecated, therefore it is in API2, probably for the reasons we’re discussing. [image]

Xojo Programming Forum

Is this normal behavior for ToString

Targets macOS

Beatrix_Willius (Beatrix Willius) July 8, 2026, 7:04am 23

Because str(variable) is API1 and variable.toString is API2.