Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!husc6!endor!siegel
From: siegel@endor.harvard.edu (Rich Siegel)
Newsgroups: comp.sys.mac.programmer
Subject: Re: ROM Unlocks handles (was Re: How to Argue Technical Points)
Message-ID: <3365@husc6.harvard.edu>
Date: 7 Dec 89 16:10:35 GMT
References: <2744@dogie.macc.wisc.edu> <3838@atr-la.atr.co.jp> <32977@ucbvax.BERKELEY.EDU> <5640@internal.Apple.COM>
Sender: news@husc6.harvard.edu
Reply-To: siegel@endor.UUCP (Rich Siegel)
Organization: Symantec Language Products Group
Lines: 31

In article <5640@internal.Apple.COM> shebanow@Apple.COM (Andrew Shebanow) writes:

>>	temp = (**hand).field;
>>	SystemCall(&temp);
>>	(**hand).field = temp;
>
>Ack! Please, please don't do this! If the system call expects a
>Handle, you should never, ever pass it a fake handle. While your

	That's not a fake handle; it's a copy of a field of a handled block.
David made no assertions about the system call's parameters; in this particular
case, it looks like the system call takes some other type of argument, but
may move memory.

	In principle, you are correct, though. Fake handles are not a good
thing.

R.


~~~~~~~~~~~~~~~
 Rich Siegel
 Staff Software Developer
 Symantec Corporation, Language Products Group
 Internet: siegel@endor.harvard.edu
 UUCP: ..harvard!endor!siegel

"There is no personal problem which cannot be solved by sufficient
application of high explosives."

~~~~~~~~~~~~~~~