> Alain: We would indeed lose the bypass-the-hierarchy
> feature of HyperTalk functions called with the
> "the" keyword. Couldn't the scripter merely "send"
the
> message to HyperCard explicitly when the bypass
> feature is deemed necessary?
Anthony: No. Send is an evil command (just like 'do'),
IMO. It's evil because it can't be parsed, tokenized,
bytecoded, or assembled with the rest of the script.
Each time a send or a do is encountered, it must be
parsed, then bytecoded, then compiled, and only then
run.
Alain: Is this an incontrovertible principle or merely
a limitation of our current approach? Your answer is
very important to me because I am in the process of
inventing an agent-based architecture where SEND is
used very very frequently.
> Alain: Or perhaps some syntax like below:
> the abs [of HyperCard] of <numericEpression>
Anthony: Well, NuParser should be able to handle it.
But it could get confusing to the user... Perhaps:
HyperCard's abs of <expr>
Alain: I like yours better. I would merely add that
the "HyperCard's" keyword is optional, like this :
[HyperCard's] abs of <expr>
1. abs of <expr> -- traverses the hierarchy
2. HyperCard's abs of <expr> -- does not traverse
Alain: That what you meant, right?
__________________________________________________
Do You Yahoo!?
Thousands of Stores. Millions of Products. All in one place.
Yahoo! Shopping: http://shopping.yahoo.com
