Scratch

Repeat until I recieve <message>
and
wait until I recience <message>
would both be *very* useful blocks.

Using variables is not quite equivalent to messages.  Plus the blocks for handling messages are better designed than the blocks for handling variables--- the pulldown lists are much handier than scrolling through the variable pane, and large numbers of variables seem to break scratch sometimes.

As an efficiency issue, if properly implemented, waiting for a message is a much more efficient daemon than waiting for an arbitrary boolean expression.  The implementation should be pretty easy, since the "when I receive" blocks are just
    forever
         wait until I  receive <msg>
         body
That is, the code for doing wait until I receive must already be implemented.

agreed, could be very useful for eliminating bugs

Last edited by astrosapien (2007-07-12 18:39:59)

I agree whole heartedly. Duncan spoke about switches which i use often but they are much harder to work and sometimes they arent suitable where a 'i receive' hexagon block would.

This will be very useful, and it was discussed before. There really should be a "when I recieve (mesage)" triangular block.

my friend and I were thinking the exact same thing!

kevin_karplus wrote:

Using variables is not quite equivalent to messages.  Plus the blocks for handling messages are better designed than the blocks for handling variables--- the pulldown lists are much handier than scrolling through the variable pane, and large numbers of variables seem to break scratch sometimes.

As an efficiency issue, if properly implemented, waiting for a message is a much more efficient daemon than waiting for an arbitrary boolean expression.  The implementation should be pretty easy, since the "when I receive" blocks are just
    forever
         wait until I  receive <msg>
         body
That is, the code for doing wait until I receive must already be implemented.

Yeah.

Also, the same is:
forever
     if I receive <msg>
            body