Transcript language design.

[Mark Wieder]

Alex-

Wednesday, June 9, 2004, 7:03:24 PM, you wrote:

AT> Often. But that's not a counter-example; that's an example of using the
AT> wrong operator and the language design not helping to spot it;   not an
AT> example of using the correct operator, which is the problem here. As I said
AT> - it caught me out mostly because string operations are so unusual.

Trying your example of:
myVar = 1
gives me:

Type    Expression: double binary operator
Object  Button 1
Line    myVar = 1
Hint    =

I don't see where this falls into the category of "the language design
not helping to spot it". Even with the buggy error handler. It's
annoying, and I'm constantly typing stuff like this and having to
correct myself, but it *does* get caught.

-- 
-Mark Wieder
 mwieder at ahsoftware.net