🚀 go-pugleaf

In article <1991May20.230908.7178@maytag.waterloo.edu> dmurdoch@watstat.waterloo.edu (Duncan Murdoch) writes:
>In article <1991May20.171545.23591@amc.com> jwbirdsa@polaris.amc.com () writes:
>>
>>   Anyone writing interrupt handlers using TC++'s "interrupt" keyword
>>should be aware that DS is not preserved into the function. DS is preserved
>>through the function; the value of DS after the interrupt is the same as
>>before. However, the value of DS while the function is executing is not the
 ....

>I don't have any of the C flavours, but I'm surprised it's not documented 
>there.  In TP, the prologue of an Interrupt procedure is explicitly given;
 ....
>Duncan Murdoch
>dmurdoch@watstat.waterloo.edu

Both my TC++ manual (PG, pg 48) and my TC2.0 manual
(UG, pg 319) state that DS is set.  What else could
be done to provide access to static data?  This `behavior'
is, practically speaking, the only one possible.
(...that is, short of allowing statics in the code
segment (ugh).  I believe MSC provides this option.)
Chalk up one more for the joys of segmented
architectures. ;->

Gene