Judy Perry writes:
> My Goodman manual (2.2) begins by explaining that commands provoke or
> commence action whereas a function (built-in or otherwise) evaluates an
> argument (say, the current status of some entity such as the clock) and
> returns a result/tells you what that status is but doesn't make any
> changes/action.
>
> I am interested in your understanding of this paragraph -- does it seem
> unclear and if so, how?
>
> (Why do I care? Because I have to create stacks explaining simple HC
> scripting and, maybe someday, do the same for MC).
That would be way cool. Good to see you on this list, Judy. You're among
the few HyperTalkers I know with UNIX experience, and with your strong
background in HyperTalk I'm sure you'll be able to contribute a lot to Rev's
growing community.
Goodman's description seems good to me as long as its written as a design
guideline rather than a functional description of the difference between the
two.
A handler can return a value (in the result) and a function can perform
actions, so newcomers might get the wrong idea with what he wrote without
some further discussion.
--
Richard Gaskin
Fourth World Media Corporation
Multimedia Design and Development for Mac, Windows, UNIX, and the Web
_____________________________________________________________________
[EMAIL PROTECTED] http://www.FourthWorld.com
Tel: 323-225-3717 ICQ#60248349 Fax: 323-225-0716
