From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fac41,c52c30d32b866eae
X-Google-Attributes: gidfac41,public
X-Google-Thread: 1108a1,c52c30d32b866eae
X-Google-Attributes: gid1108a1,public
X-Google-Thread: 103376,2ea02452876a15e1
X-Google-Attributes: gid103376,public
From: bobduff@world.std.com (Robert A Duff)
Subject: Re: Real OO
Date: 1996/05/03
Message-ID: <Dqtz2D.AFH@world.std.com>#1/1
X-Deja-AN: 152781437
references: <DqsEt9.8Hv@world.std.com> <Dqt4BM.7up@assip.csasyd.oz>
organization: The World Public Access UNIX, Brookline, MA
newsgroups: comp.lang.eiffel,comp.lang.ada,comp.object
Date: 1996-05-03T00:00:00+00:00
List-Id: <comp.lang.ada>


In article <Dqt4BM.7up@assip.csasyd.oz>,
Don Harrison <donh@syd.csa.com.au> wrote:
>In 'Ziggy', you would just write:
>
>op (a: separate A; b: separate B) is ... end       -- locks a and b atomically
>
>No need for a wrapper.

Sorry I wasn't clear.  Yes, I understand the above.  My question was,
how does the person writing the Ziggy compiler/run-time system
*implement* this "simultaneous" locking of a and b?  At the machine-code
level, I mean?

- Bob