On Thursday 28 September 2006 11:25, Allison Randal wrote: > Exactly, change the most common case (of a method call by bare name) to > be the unmarked case, and use some additional marking on the less common > case of calling a method by a string name or method object. I wouldn't > use '$' to mark the string lookup because it's too confusing with the > temporary register variables ($S0, etc). But some other syntactic sugar > would work. This is clumsy, but then, it's also rare. > > obj.{bar}() # a string method name > obj.{$S1}()
That's not bad; it reminds me a bit of Perl and Tcl. To push a little more the other direction, is it possible for the compiler to detect symbol and method name conflicts? It's only the collision that makes a case ambiguous, right? -- c