home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!concert!uvaarpa!adastra!mbs
- From: mbs@adastra.cvl.va.us (Michael B. Smith)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: RKM description of WaitPort()
- Distribution: world
- Message-ID: <mbs.1iv3@adastra.cvl.va.us>
- References: <1993Jan1.221013.26070@urbana.mcd.mot.com>
- X-NewsSoftware: GRn-beta 1.16g (01.01.93) by Michael B. Smith & Mike Schwartz
- MIME-Version: 1.0
- Content-Type: text/plain; charset=iso-8859-1
- Content-Transfer-Encoding: 8bit
- Date: 2 Jan 93 09:44:52 EST
- Organization: Well, I haven't decided on a name yet...
- Lines: 19
-
- In article <1993Jan1.221013.26070@urbana.mcd.mot.com> qbarnes@urbana.mcd.mot.com (Quentin Barnes) writes:
- > I was reading the description of the WaitPort() call in the RKM:Libraries
- > and was confused by the description. On page 504, it says:
- >
- > ... It is possible to receive a signal for a port without
- > a message being present yet. The code processing the
- > messages should be able to handle this. ...
- >
- > It seems to me to OS is waking up the task before it has attached the
- > message to the specified port and it would be up the the application
- > to spin on the GetMsg() call until the message generating the signal
- > showed up. This seems terribly wrong and the example code does not
-
- The word "yet" should be deleted. Do NOT spin on GetMsg(). Instead,
- gracefully handle the situation where GetMsg() == NULL, which *is* done
- by the example on page 505 under "Getting a Message".
- --
- // Michael B. Smith
- \X/ mbs@adastra.cvl.va.us -or- uunet.uu.net!virginia.edu!adastra!mbs
-