Path: utzoo!attcan!uunet!ginosko!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!hoptoad!tim
From: tim@hoptoad.uucp (Tim Maroney)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Integer Size problem
Message-ID: <8386@hoptoad.uucp>
Date: 24 Aug 89 18:06:36 GMT
References: <15141@dartvax.Dartmouth.EDU> <11689@cit-vax.Caltech.Edu> <1465@draken.nada.kth.se> <13727@polyslo.CalPoly.EDU> <1478@draken.nada.kth.se>
Reply-To: tim@hoptoad.UUCP (Tim Maroney)
Organization: Eclectic Software, San Francisco
Lines: 21

In article <1478@draken.nada.kth.se> d88-jwa@nada.kth.se (Jon W{tte) writes:
>That's right, USER interrupt routines can't shuffle memory. But try tracing
>a _HLock or something like it in MacsBug. You'll see that all Handle handling
>is part of DoVBLTask (At least on my SEx and MacsBug 6.0, might be that the
>procedure names are wrong for thia ROM ?)

The procedure names are best guess approximations.  When you see the PC
in DoVBLTask, all that means is that the nearest symbol Macsbug knows of
is DoVBLTask.  If you spend much time stepping through code in the ROM,
you'll find that the names are wrong as often as they're right.

>I think that interrupts in the OS shuffle data, but ours may not. Damned
>segregation ! ,-)

No, no, no.  Interrupt driven code does not allocate or shuffle memory.
Period.
-- 
Tim Maroney, Mac Software Consultant, sun!hoptoad!tim, tim@toad.com

"Those who restrain desire, do so because theirs is weak enough to be
 restrained..." - Blake, "The Marriage of Heaven and Hell"