Article View: comp.sys.sequent
Article #693s_lock vs S_LOCK
From: Steve Hammond
Date: Wed, 07 Sep 1988 17:31
Date: Wed, 07 Sep 1988 17:31
18 lines
1314 bytes
1314 bytes
I am having trouble using s_lock() vs. the in-line macro S_LOCK.
I have looked at the code for the macro but don't see the
problem. I have been using s_lock() without any trouble but
felt I could use the speed up of having in-line macro instead
of making the 100k procedure calls that my application required.
Rather than fill this newsgroup with details of my probelm, I would
prefer to correspond with someone via e-mail and then I will post
a summary of what I have learned... So, if you have successfully
used S_LOCK could you let me know and I will tell you what
behaviour I am observing. I appreciate the help. Thanks.
Steve
--------------------------------------------------------------------
Steve Hammond RPI CS Dept. hammonds@turing.cs.rpi.edu
--------------------------------------------------------------------
Technical Details
Message-ID:
<1138@imagine.PAWL.RPI.EDU>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!mordor!joyce!ames!nrl-cmf!ukma!psuvm.bitnet!cunyvm!nyser!itsgw!imagine!turing.cs.rpi.edu!hammondsShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!lll-winken!lll-tis!mordor!joyce!ames!nrl-cmf!ukma!psuvm.bitnet!cunyvm!nyser!itsgw!imagine!turing.cs.rpi.edu!hammonds From: hammonds@turing.cs.rpi.edu (Steve Hammond) Newsgroups: comp.sys.sequent Subject: s_lock vs S_LOCK Message-ID: <1138@imagine.PAWL.RPI.EDU> Date: 7 Sep 88 17:31:21 GMT Sender: news@imagine.PAWL.RPI.EDU Reply-To: hammonds@turing.cs.rpi.edu (Steve Hammond) Organization: RPI CS Dept. Lines: 17