Article View: comp.sys.next.programmer
Article #1753NeXTstep 2.1 kernel threadsafe?
From: Jeff S. Sargent
Date: Tue, 06 Oct 1992 02:57
Date: Tue, 06 Oct 1992 02:57
7 lines
958 bytes
958 bytes
Is the NeXTstep 2.1 kernel threadsafe? The threads documentation encourages you to bracket most lib calls with mutex semaphores, but what about functions like msg_send and msg_rcv? Apparently in 3.0, the kernel is threadsafe, but non-kernal OS fnctions like the nameserver are not. Also a special call is needed to make the Objective-C runtime threadsafe. I'm concerned about these details in 2.1, 2.2 at the moment.
Technical Details
Message-ID:
<1992Oct6.025718.19262@gagme.chi.il.us>Path:
arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!wupost!usc!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!nucsrl!ddsw1!serveme!gagme!sargentShow Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.programmer Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!wupost!usc!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!nucsrl!ddsw1!serveme!gagme!sargent From: sargent@gagme.chi.il.us (Jeff S. Sargent) Subject: NeXTstep 2.1 kernel threadsafe? Message-ID: <1992Oct6.025718.19262@gagme.chi.il.us> Originator: sargent@gagme Lines: 7 Sender: sargent@gagme.chi.il.us (Jeff S. Sargent) Organization: Gagme Public Access UNIX, Chicago, Illinois. Distribution: usa Date: Tue, 6 Oct 1992 02:57:18 GMT