Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!jarthur!uunet!glyph!ahh
From: ahh@glyph.UUCP (Andy Heffernan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: GetMsg, PutMsg - Question
Summary: woof
Message-ID: <503@glyph.UUCP>
Date: 24 Feb 90 00:31:37 GMT
References: <3197@ssc-vax.UUCP>
Reply-To: ahh@glyph.UUCP (Andy Heffernan)
Organization: Cinnamon Toast Crunch Research Labs
Lines: 14

In article <3197@ssc-vax.UUCP> dano@ssc-vax.UUCP (Dan Olson) writes:
>Just curious, do GetMsg and PutMsg automatically Forbid so that two
>tasks cannot accidently muck each other up if there just happens to
>be task switching while both tasks are hacking at the same port.

Actually, they DISABLE on entry and ENABLE on exit since they fool
with the list of messages attached to a given MsgPort, and an interrupt
routine could sneak in and attach a message to that MsgPort if the
routine was merely forbidden.

-- 
-------------------------------------------------------------------------
  Andy Heffernan					uunet!glyph!ahh
"'Iodine!' shrieked Clavius the Mage.  'I must have iodine!'"