Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-unix!ctnews!pyramid!voder!apple!winkler
From: winkler@apple.UUCP (Dan Winkler)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: SetGlobal stupidity
Message-ID: <7241@apple.UUCP>
Date: 21 Jan 88 19:06:29 GMT
References: <AVxAUwy00Xo1Mxs0Ns@andrew.cmu.edu>
Reply-To: winkler@apple.UUCP (Dan Winkler)
Organization: Apple Computer Inc., Cupertino, USA
Lines: 12

> The semantics of the SetGlobal call from an XCMD are not the same as the
> semantics of setting a global variable through HyperTalk.  If the global
> variable does not already exist, calling SetGlobal on it does nothing but
> cause a SysBeep (some error message!).  I can't find any way of creating a
> global variable with a computed name except temporarily replacing the script
> of something with the appropriate HyperTalk code.

Oops...  Sorry about that.  This is true and it's a bug.  SetGlobal
should obviously create a global if it needs to.  I'll fix it in a
future release.

Dan.