Re: OODL: Prototyping OpenTalk syntax - hierarchy

[DeRobertis]

At 6:42 AM -0700 on 12/3/99, Rob Cozens wrote:
>>I think the do command, the send command, and any run-time
>>variable naming should be left in the scrap heap of history.
>
>Anthony, et al:
>
>I occasionally use all three; though my main concern would be loss of send,
>unless we have another method of bypassing the normal message passing
>hierarchy.

The evil of the send command is when it is used like this:

        send variable&variable2&&quote&variable3&quote to whatever

I don't have a proble mbypassing the message hierarchy; that can be done
easily. I do have a problem with building commands at runtime.

>
>Want to guess how many existing HC stacks become incompatible with OC if we
>don't support do, send, and run-time variable naming?

Not too many. Most I've seen don't make use of do. Most that use send only
use it to send a mouseup to a button; quick fix will work there.

As for runtime variable naming, hashes can be used instead. A fairly quick fix.