Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!dewey.soe.berkeley.edu!oster
From: oster@dewey.soe.berkeley.edu (David Phillip Oster)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MenuChoice (was Hierarchical menu question)
Message-ID: <29202@ucbvax.BERKELEY.EDU>
Date: 17 May 89 02:21:54 GMT
References: <DES.89Apr27123344@orenda.amara.uucp> <1579@internal.Apple.COM> <30697@apple.Apple.COM> <7303@hoptoad.uucp>
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: oster@dewey.soe.berkeley.edu.UUCP (David Phillip Oster)
Distribution: na
Organization: School of Education, UC-Berkeley
Lines: 12

In article <7303@hoptoad.uucp> tim@hoptoad.UUCP (Tim Maroney) writes:
>In article <30697@apple.Apple.COM> tecot@Apple.COM (Ed Tecot) writes:
>>As a side note, I'd point out that the use of globals is strongly discouraged;
>>even assembly hackers should use MenuChoice.

>Except that, despite its inclusion in Inside Mac V, it is not implemented
>and quite possibly never will be.

I don't know what Tim is thinking of on this one. I'm sitting here on a
Mac IIcx. Macsbug says MenuChoice is trap AA66, and that it is two
instructions: move from the low memory global to the function return cell,
return.