2010/2/24 Lukas Renggli <[email protected]>: >> Huh? I am always assumed that binary selectors parsed in greedy >> manner, which means that if parser found the start of >> binary selector, it scans forward for following characters which can >> be part of selector, without exceptions, like '-' char.. > > I checked in the ANSI standard. Igor is right: > > == ANSI: 3.5.6 Numbers ====== > > binaryCharacter ::= '!' | '%' | '&'' | '*' | '+' | ','' | '/' | '<' > | '=' | '>' | '?' | '@' | '\' | '~' | '|' | '-' > binarySelector ::= binaryCharacter+ > > Binary selectors are method selectors that appear similar to > mathematical operators. A binary selector may be any length greater > than or equal to one. If a negative <number literal> follows a binary > selector there must intervening white space." > > ========================= > > I somehow remembered the grammar differently and that the $- was only > allowed in the first position. This doesn't seem to be the case though > (any longer) :-/ > > I am not against changing the grammar to conform to ANSI and VW. I > think that would actually be a good move, even if it is probably not > really relevant in practice. I am however strongly against asking the > user to disambiguate an expression. The compiler should compile what > the user types, not guess what else he could have ment to say. > > Lukas >
Then the question is how you compile 1...@-2 and how you provide backward compatibility. Nicolas > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
