delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1996/05/01/18:12:06

Xref: news2.mv.net comp.os.msdos.djgpp:3304
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Library reference for djgpp
Date: Tue, 30 Apr 1996 15:25:32 CDT
Organization: Rice University, Houston, Texas
Lines: 15
Message-ID: <3186773c.sandmann@clio.rice.edu>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960430134315 DOT 2944E-100000 AT is>
Reply-To: sandmann AT clio DOT rice DOT edu
NNTP-Posting-Host: clio.rice.edu
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

> >   I think what he means are variables like __djgpp_ds_alias, __djgpp_dos_sel,
> > __djgpp_exception_state, routines like __djgpp_raise_exception and such. 
> Only if ``the full power'' is related to signals and interrupts.

One of the reasons these things were never documented is that I was never
fully satisfied with the code, planned a re-write, and thus they would be
renamed/deleted/changed.  For example, the exception structure went from
a static name in an early beta to a pointer to a chain of structures in 
the release.  When it got close to release time and it became obvious the
planned rewrite would not happen, there wasn't much time for documenting the
really obscure stuff.  I never expected that anyone would want to get in
and mess with something at that low a level.  There are still some windows
of badness in the HW interrupt to exception code if the DPMI provider has
bugs and doesn't follow the rules (like the QDPMI problem with CTRL-C ;-P )
which I would have liked to fix, but ...

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019