Date: Tue, 2 May 2000 19:27:41 +0200 (WET)
From: Andris Pavenis <pavenis AT lanet DOT lv>
To: Pierre Muller <muller AT cerbere DOT u-strasbg DOT fr>
cc: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Subject: Re: interrupt 0x75 limitation in Win95 ?
In-Reply-To: <200005021646.SAA07021@cerbere.u-strasbg.fr>
Message-ID: <Pine.A41.4.05.10005021926290.49264-100000@ieva05.lanet.lv>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk



On Tue, 2 May 2000, Pierre Muller wrote:

> At 14:28 02/05/00 +0300, Eli Zaretskii wrote:
> >>    This Win95 limitation can be important for programs using C++
> exceptions !!
> >
> >How are C++ exceptions related to this issue?  I don't think they use the 
> >FP exception or signals, do they?
> 
>    I don't know about C++ but in Delphi object pascal apparently
> the FPU exceptions are converted into software exception that can be handled
> like any other sofware exceptions and thus need to be
> able to support multiple time calls, which is the origin
> of this whole thread. 
> 

They are not related. FP exceptions and signals are not used to implement
C++ exception. 

Andris