As long as I know that I have do "b call(8)" instead of "b(8)", it's
not that bad. Of course there should have been a few words about this
feature in the docs, but I found nothing. I found some postings about
"activatable" on the list around the middle of July, but I didn't
find the "final declaration" or anything about the reason for this
feature.
/Jon
>Many months ago blocks were made non-activatable by default. Methods
>still activate by default, but blocks don't. It's annoying, isn't it?
>
>On 12-Dec-06, at 3:16 AM, Jon Kleiser wrote:
>
>>When I use Io-2006-12-07 (which presents itself as Io 20061114 in my
>>PPC Mac terminal window), I can do the following:
>>
>>Io> b := block(x, (x+2) println)
>>
>>==> block(x, (x +(2)) println)
>>Io> b(8)
>>
>>==> block(x, (x +(2)) println)
>>Io> m := method(x, (x+2) println)
>>
>>==> method(x, (x +(2)) println)
>>Io> m(8)
>>10
>>
>>==> 10
>>
>>As you can see, when I try to execute b(8), I only get the block b
>>back, no execution. I guess this is a bug.
>>When I do the same with a method, it works like in the old days.
>>
>>/Jon
...
>Jeremy Tregunna
.