binary selectors ambiguity and space
ncellier at ifrance.com
Mon May 15 11:26:31 UTC 2006
Le Lundi 15 Mai 2006 07:41, Wolfgang Helbig a écrit :
> The Scanner>>xBinary method should not at all accept expressions like
> "x+-3". Instead it should kindly ask the programmer to resolve the
> ambiguity by inserting white space. Without taking a default action.
> Expressions are ambiguous, if a minus character can be parsed both as the
> second character of a binary selector and as the first character of a
> number literal.
> If the folks start grumbling at this pedantry tell them Monk was here :-)
> Weniger, aber besser.
I totally agree,
user shall be kindly invited to, for code he has responsibility on.
That is, when he accepts a method in a browser debugger or any other
interactive text pane.
But this turn out very annoying when you get warned 20 times or more that you
should resolve ambiguity over wich you do not have control yet, for example
when you try to load a package from SqueakMap or Monticello.
This is why i propose the notification to raise a popup dialog only if
Parser>>interactive answer true.
This is exactly the same when temporary variables names clash with inst var
names: you cannot accept the method interactively, but you can when you load
it from any repository.
See senders of #interactive.
More information about the Squeak-dev