On 03-03-2013, at 2:39 AM, Frank Shearar <frank.shearar at gmail.com> wrote:

> On 3 March 2013 02:23, Bob Arning <arning315 at comcast.net> wrote:
>> I think you'll find that now works as you expect with the code I posted
>> earlier (once you use the #findSelector2 instead of #findSelector).
>> 
>> After posting the code I started wondering about other possible odd
>> situations, like what is expected from
>> 
>> self x: 1; y: 2
>> 
>> Right now it considers the selector to be #x:y: . Easy enough to fix, but is
>> the right answer #x:, #y: or nothing?
> 
> A menu that pops up asking you which one you meant?

Better yet, modify the system to be able to deal with all three cases and display the results sensibly in a browser.
Multiple browsers might be an acceptable option, one for each possible case.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
As far as we know, our computer has never had an undetected error.