| delorie.com/archives/browse.cgi | search |
| Date: | Sun, 2 Apr 2000 10:01:31 +0200 (IST) |
| From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
| X-Sender: | eliz AT is |
| To: | Jonathan Meunier <jonathanm AT corel DOT com> |
| cc: | djgpp AT delorie DOT com |
| Subject: | Re: Interrupt wrapper (was Re: keyboard interrupt) |
| In-Reply-To: | <38E0DC7C.CE330DAB@corel.com> |
| Message-ID: | <Pine.SUN.3.91.1000402100047.9367U-100000@is> |
| MIME-Version: | 1.0 |
| Reply-To: | djgpp AT delorie DOT com |
| Errors-To: | nobody AT delorie DOT com |
| X-Mailing-List: | djgpp AT delorie DOT com |
| X-Unsubscribes-To: | listserv AT delorie DOT com |
On Tue, 28 Mar 2000, Jonathan Meunier wrote: > > > But what exactly is a wrapper; why do we need one? > > > > I already answered this question... Since, DJGPP/GCC doesn't support > > definitions of Interrupt Service Routines (using "interrupt" reserved > > word or something similar) with register save/load, ... and IRET(D), we > > should do this with ASM. Clear? > > Oh, sorry, I just thought a wrapper would do more than that.. It *does* do more than that. I suggest a good look at the library docs and at the wrapper sources.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |