Mail Archives: djgpp/1999/02/08/06:19:58
On Mon, 8 Feb 1999, Eli Zaretskii wrote:
> > But then again, with 2 "simple" handlers,
> > will I need to manually deallocate the iret wrapper ? (curiosity only...
>
> The same considerations as in the case of a single handler apply here.
> It doesn't mattter how many handlers for different interrupts do you
> have.
ok...
> > BTW also, the allegro macros LOCK_CODE and LOCK_DATA, are internally
> > calling the _go32 functions lock_code and lock_data ?
>
> Yes, they do. But you could easily have established that yourself, by
> looking at the sources. That is the beauty of free software, after all.
argh! I had archived them somehwere and the archive now has a CRC error!
I'll have to download them again! :))
> > 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...)
>
> No, locking means that the locked portion of memory cannot be paged out
> by the virtual memory mechanism.
excellent then... that was what I supposed...
thanks then... bye...
Isaac Santaolalla
_________________________________________________________________________
_______________________________________________________________________
UNIX is user friendly. It's just selective about who its friends are.
_______________________________________________________________________
- Raw text -