I wasn't aware Len was an operator. I thought it just returned the length of strings like in every other language I've ever used. :-)
"The precedence of the . (member access operator) is documented as being higher than the Len operator"
So then:
"font.text "("+Len(w.txt).ToString()+")",x,y"
Should do (w.txt).ToString(), and Len should then operate on the resulting string.
I don't like this though. I code assuming Len() is a function because of years of conditioning. I see there that Asc and Chr are also operators now? WHY? Can you do Asc on anything other than a string? Can you convert anything BUT a number to a Chr$()? Why change things just for the sake of changing them and confusing the hell out of people when stuff doesn't work?
If "font.text "("+Len(w.txt).ToString()+")",x,y" doesn't work now, and it's because Len is now a function and the . no longer takes precedence, then I'm FINE with that. That's how I'd expect it to work.
"The precedence of the . (member access operator) is documented as being higher than the Len operator"
So then:
"font.text "("+Len(w.txt).ToString()+")",x,y"
Should do (w.txt).ToString(), and Len should then operate on the resulting string.
I don't like this though. I code assuming Len() is a function because of years of conditioning. I see there that Asc and Chr are also operators now? WHY? Can you do Asc on anything other than a string? Can you convert anything BUT a number to a Chr$()? Why change things just for the sake of changing them and confusing the hell out of people when stuff doesn't work?
If "font.text "("+Len(w.txt).ToString()+")",x,y" doesn't work now, and it's because Len is now a function and the . no longer takes precedence, then I'm FINE with that. That's how I'd expect it to work.