You know what I'm going to say.
Yeah good point. I think we knew that, but it's never gotten up to the top of the list to fix. Thanks for pinging it.
Are you suggesting that Snap! should evaluate b * f and c * e and then subtract 2nd result from the 1st?
Why do you not read the blocks as (((b * f) - c) * e)
Not if you read them as being surrounded by ( )
( ) stop ambiguity
Totally on purpose. Operator precedence is the source of all evil in Maths education (e.g. German kids learn the rule "dot comes before line, which doesn't map to the conventions in other countries) and in
programming languages. If you want precedence in any serious, well designed system, use parens, which you can use in this field, in case you didn't know.
This was the second reason (besides the weird character set) why APL didn't take over the world. I don't think it would be so terrible to give users the behavior they expect.
yep i didnt