home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: sparky!uunet!elroy.jpl.nasa.gov!jato!jdickson
- From: jdickson@jato.jpl.nasa.gov (Jeff Dickson)
- Subject: Re: IPC and shared memory
- Message-ID: <1993Jan4.220638.12229@jato.jpl.nasa.gov>
- Organization: Jet Propulsion Laboratory
- Distribution: comp.sys.amiga.programmer
- Date: Mon, 4 Jan 1993 22:06:38 GMT
- Lines: 28
-
- I wrote:
-
- >> IMHO FindSemaphore is a waste of time if your usage of it is purely
- >> for the convenience of knowing it by name. I suggest simply making
- >> the signal semaphore globally known or just to the tasks/processes
- >> that wish to use it and forgo the FindSemaphore bit all together.
-
- paulk@terapin.com (Paul Kienitz) writes:
-
- >HOW do you "make it globally known"?? That's what the name is for.
-
- Declare the Signal Semaphore structure itself or a pointer to it in your
- main program's data area and then restore that area in any sub tasks/pro-
- cesses that wish to gain access to the semaphore. Under Manx Aztec C this
- is a simple matter of restoring register A4. Use InitSemaphore instead
- of AddSemaphore. Actual usage is no different.
-
- Jeff
-
-
-
-
-
-
-
-
-
-
-