From: alaric AT abwillms DOT demon DOT co DOT uk (Alaric B. Williams)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Hardware Interrupts with C: Locking
Date: Thu, 19 Dec 1996 19:26:39 GMT
Lines: 34
Message-ID: <851023575.14651.0@abwillms.demon.co.uk>
References: <BE43E04CAE AT merlin2 DOT e-technik DOT uni-erlangen DOT de>
NNTP-Posting-Host: abwillms.demon.co.uk
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

"Michael Schuster" <Schuster AT eev DOT e-technik DOT uni-erlangen DOT de> wrote:

>Gruess Dich Thomas!

>> Out of the blue:
>> 
>> Do you ever lock data, or your handler routines?
>Yes I did it with allegro's lock_variable() and lock_function makro.
>Now, using short **data, the programm is still so small, 
>that everything works fine, even if not locking it. (I have 20 MB 
>RAM) 

Remember that if you have a pointer, then not only do you have to lock
the pointer, you must lock the data pointed to... and if you have
"short**", the presumably you've allocated an array of "short*"s for
it to point to, and in turn a set of arrays of "short"s. All of these
things must be locked!

Luck,


ABW
--

"Simply drag your mother in law's cellphone number from the
Address Book to the Laser Satellite icon, and the Targeting
Wizard will locate her. Then follow the onscreen prompts for
gigawattage and dispersion pattern..."

(Windows for Early Warning and Defence User's manual P385)

Alaric B. Williams Internet : alaric AT abwillms DOT demon DOT co DOT uk
<A HREF="http://www.abwillms.demon.co.uk/">Hello :-)</A>