home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!mcdchg!mcdphx!udc!qbarnes
- From: qbarnes@urbana.mcd.mot.com (Quentin Barnes)
- Subject: RKM description of WaitPort()
- Message-ID: <1993Jan1.221013.26070@urbana.mcd.mot.com>
- Sender: news@urbana.mcd.mot.com (News)
- Nntp-Posting-Host: neptune.urbana.mcd.mot.com
- Organization: Motorola Computer Group, Urbana Design Center
- Date: Fri, 1 Jan 1993 22:10:13 GMT
- Lines: 16
-
- 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
- do this. What am I missing? What does the documentation actually
- saying?
- --
- Quentin Barnes
- qbarnes@urbana.mcd.mot.com | ..!uiucuxc!udc!qbarnes
-