binary selectors ambiguity and space
ncellier at ifrance.com
Mon May 15 20:27:33 UTC 2006
Le Lundi 15 Mai 2006 20:42, Stephan Rudlof a écrit :
> On 15.05.2006 20:25, I wrote:
> > On 13.05.2006 02:10, nicolas cellier wrote:
> > nc>...
> > nc> Funny, in current 3.9 spaces are ignored:
> > nc> i have '1 +- 2' interpreted as (1) + (-2)
> > At least, if there should be a change in the semantics - for e.g.
> > allowing selector #+- in the case above -, it would be *much* better to
> > fail loading a package instead of loading it silently: otherwise the
> > code would just break at runtime!
> After sending this comment I've seen, that this example is far from the
> case: so for such a semantic change there should be
> - an announcement,
> - a code snippet for scanning the code for cases, where the semantics is
> announced to be changed.
> Since after changing the semantics this way, the above would not have
> any ambiguity, and therefore it would be loaded smoothly...
Notification subclass: #PrefixUnarySelectorNotification
hereType == #word
[parseNode := self variable.
(parseNode isUndefTemp and: [self interactive])
ifTrue: [self queryUndefined].
hereType == #leftBracket
hereType == #leftBrace
hereType == #leftParenthesis
self expression ifFalse: [^self expected: 'expression'].
(self match: #rightParenthesis)
ifFalse: [^self expected: 'right parenthesis'].
(hereType == #string or: [hereType == #number or: [hereType == #literal]])
[parseNode := encoder encodeLiteral: self advance.
(here == #- and: [tokenType == #number])
"not very clean hack to check for space.
beside, hereMark/prevMark are broken at end of stream"
hereMark > (prevMark+1) ifTrue: [PrefixUnarySelectorNotification
signal: '- is used as unary prefixed selector'].
parseNode := encoder encodeLiteral: self advance negated.
| report |
report := (String new: 128) writeStream.
Smalltalk keysAndValuesDo: [:name :cls |
(cls isKindOf: Behavior)
ifTrue: [(Array with: cls with: cls class)
do: [:class | class selectorsDo: [:selector |
[class compilerClass new
parse: (class sourceCodeAt: selector)
in: class notifying: nil]
do: [:exc |
print: class; nextPutAll: #'>>';
nextPutAll: selector; cr]]]]].
report contents inspect.
It was not that easy, because handling is done lately, with two tokens of
I didn't find anything in 3.9a7029... So, this must be quite unusual.
Would be funny to scan a Monticello repository or SqueakMap...
(above my skills).
More information about the Squeak-dev