Date:	Mon, 8 Feb 1999 10:31:43 +0000 (GMT)
From:	=?iso-8859-1?Q?Isaac_Santaolalla_Sol=F3rzano?= <is05562 AT salleURL DOT edu>
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	djgpp AT delorie DOT com
Subject:	Re: keyboard handler...
In-Reply-To:	<Pine.SUN.3.91.990204133111.7801N-100000@is>
Message-ID:	<Pine.LNX.3.96.990208102507.13526A-100000@cygnus.salleURL.edu>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com

On Thu, 4 Feb 1999, Eli Zaretskii wrote:

> > BTW also, a new doubt came to me... If I "allocate" an IRET wrapper, MUST I
> > deallocate it explicitly?
> 
> If you only allocate it once, and use the handler until the program
> exits, then you don't need to bother.  It is deallocated automatically
> for you when the program exits.

ok then... but anyway, as some other people told me that it never hurts to
deallocate it manually at the end of the program, I'll do it. Besides, I'm
also planning changing allegro timer routines, with my own handler (now
that I know how to do it! :) But then again, with 2 "simple" handlers,
will I need to manually deallocate the iret wrapper ? (curiosity only...
I'll use the deallocate function even it may not be necessary...)

BTW also, the allegro macros LOCK_CODE and LOCK_DATA, are internally
calling the _go32 functions lock_code and lock_data ? Reading the info
pages about lock functions, it didn't remained clear to me that these
functions are intended to avoid swapping, but to ACTUALLY lock them (i.e.
no one will be able to touch them...) Maybe I'm confused...

I don't know... thanks again...
    
    						Isaac Santaolalla
  _________________________________________________________________________
   _______________________________________________________________________
   
    UNIX is user friendly. It's just selective about who its friends are.
   _______________________________________________________________________

- Raw text -