H
Hamish Dean
Hi. To explain this, i'll list some relevant info:
Prog1: A c++ dll, written by me.
Prog2: A c++ dll, written by a 3rd party.
Prog3: A c++ application, written by me.
Prog4: A delphi 7 application, written by me.
Prog5: A delphi 4 application, written by someone else.
Prog1 calls a function from Prog2:
try{
DoSomething() /*call to Prog2*/
}
catch(...){};
Prog3,4,5 all call the same function from Prog1, with the same input
variables.
Prog3,4 both run successfully, no issues.
Prog5 says "Floating point overflow". This occurs somewhere in the
DoSomething function, which I obtained from a 3rd party.
Is this not an exception?? how come catch(...){} does not handle this?
I am stumped as to how to fix this. Any advice appreciated.
Hamish
I've written a .dll in c++ (ProgA). At some point, ProgA
Prog1: A c++ dll, written by me.
Prog2: A c++ dll, written by a 3rd party.
Prog3: A c++ application, written by me.
Prog4: A delphi 7 application, written by me.
Prog5: A delphi 4 application, written by someone else.
Prog1 calls a function from Prog2:
try{
DoSomething() /*call to Prog2*/
}
catch(...){};
Prog3,4,5 all call the same function from Prog1, with the same input
variables.
Prog3,4 both run successfully, no issues.
Prog5 says "Floating point overflow". This occurs somewhere in the
DoSomething function, which I obtained from a 3rd party.
Is this not an exception?? how come catch(...){} does not handle this?
I am stumped as to how to fix this. Any advice appreciated.
Hamish
I've written a .dll in c++ (ProgA). At some point, ProgA