Date: Tue, 13 Aug 1996 08:47:13 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Bruce Foley <brucef AT central DOT co DOT nz>
Cc: djgpp AT delorie DOT com
Subject: Re: When should I "LOCK" data/code?
In-Reply-To: <4un53i$72j@status.gen.nz>
Message-Id: <Pine.SUN.3.91.960813084538.28748H-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 12 Aug 1996, Bruce Foley wrote:

> I understand this, but having looked at code such as that in ALLEGRO,
> I notice that just about everything gets locked!  Are there any hard
> and fast rules defining what should/shouldn't get locked when
> developing an application?

You should lock any code that gets executed (directly or indirectly) by 
the hardware interrupt handlers, and any data which the handlers might 
access.