Xref:	news2.mv.net comp.os.msdos.djgpp:7127
From:	brucef AT central DOT co DOT nz (Bruce Foley)
Newsgroups:	comp.os.msdos.djgpp
Subject:	When should I "LOCK" data/code?
Date:	Mon, 12 Aug 1996 10:46:45 GMT
Organization:	Internet Company of New Zealand
Lines:	17
Message-ID:	<4un53i$72j@status.gen.nz>
NNTP-Posting-Host:	brucef.central.co.nz
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Hi.  A while ago I was following a thread that discussed locking data
& code.  From this I managed to derive that locking code & data was
primarily related to interrupts.  That is, any data or code associated
with an interrupt should not be allowed to be swapped out by the OS.

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?  Does "locking" serve more of a purpose
than the one I have noted above?

Thanx,

Bruce.

- Raw text -