The precedence of . is high, thats correct. Nearly highest after all
But there is no question about precedence in this problem
len(x.txt) is a function. It gets executed before ANY precedence questions come up at all.
And the return of this function (-> int) then is used to execute the following procedure. And as int is no object it fails. No mather if + is higher than . or . higher than boolean or anything.
Can't remember that it ever worked at all.
.ToString() is a method I never called anyway, as it is an implicitely called method on objects anyway if they are used in a string context and thus it does not make sense. (sure there are some that want to explicitely cast anything. To me only makes sense if the code is that messy that the variable type isn't clear when writting the code so you can prevent "wrong casts")
If you've used modern languages, you are used to not manually call this method anyway as it is one of the objects core methods and its the same in BM.
But there is no question about precedence in this problem
len(x.txt) is a function. It gets executed before ANY precedence questions come up at all.
And the return of this function (-> int) then is used to execute the following procedure. And as int is no object it fails. No mather if + is higher than . or . higher than boolean or anything.
Can't remember that it ever worked at all.
.ToString() is a method I never called anyway, as it is an implicitely called method on objects anyway if they are used in a string context and thus it does not make sense. (sure there are some that want to explicitely cast anything. To me only makes sense if the code is that messy that the variable type isn't clear when writting the code so you can prevent "wrong casts")
If you've used modern languages, you are used to not manually call this method anyway as it is one of the objects core methods and its the same in BM.