Board index » kylix » Re: New unofficial VisualCLX patch version 3.5 released

Re: New unofficial VisualCLX patch version 3.5 released


2004-06-09 05:18:56 AM
kylix1
Hi,
Quote
I understand that variable c looks like integer indefinite values but algebraic rules for Nan do not work in this case. E.g for Double we have Nan+1=Nan, Nan-1 =Nan etc. , For currency
Nan-1=Nan (-922337203685477.5808), Nan+1= -922337203685476.5808<>-922337203685477.5808.
Agreed, that's not very useful. The problem is that Integer indefinite
at the same time is a valid integer value, quite different from the
situation with FPU floating point data types.
My point was that, while this might be neither useful nor satisfying, it
is completely explicable and not as weird as it might seem at first glance.
And why do you mask the FPU exceptions in the first place? I still don't
understand your exact problem. QC 8356 is a bad bug report, it doesn't
tell me what happens exactly. "FPU exceptions do not work"? How
specifically? "Atention now this program will die"? Do I really need to
run the example code to find out?
Robert
 
 

Re:Re: New unofficial VisualCLX patch version 3.5 released

Robert Rossmair < XXXX@XXXXX.COM >wrote:
Quote
Hi,

>I understand that variable c looks like integer indefinite values but algebraic rules for Nan do not work in this case. E.g for Double we have Nan+1=Nan, Nan-1 =Nan etc. , For currency
>Nan-1=Nan (-922337203685477.5808), Nan+1= -922337203685476.5808<>-922337203685477.5808.

Agreed, that's not very useful. The problem is that Integer indefinite
at the same time is a valid integer value, quite different from the
situation with FPU floating point data types.

My point was that, while this might be neither useful nor satisfying, it
is completely explicable and not as weird as it might seem at first glance.

And why do you mask the FPU exceptions in the first place? I still don't
understand your exact problem. QC 8356 is a bad bug report, it doesn't
tell me what happens exactly. "FPU exceptions do not work"? How
specifically? "Atention now this program will die"? Do I really need to
run the example code to find out?

Robert
ShowMessage('Step1: 8087CW='+IntToStr(Get8087CW));//CW=$1372
try
d:=0.0;
d:=1.0/d;
except
on E:Exception do
ShowMessage('Step2: 8087CW='+IntToStr(Get8087CW)+' d='+FloatToStr(d)+' '+E.Message); //CW=$1372
end;
SQLConnection1.Connected:=true;
ShowMessage('Step3: 8087CW='+IntToStr(Get8087CW)+' Attention now this program will die!');//CW=$1372
//I want to catch exception this but the program go out.
try
d:=0.0;
d:=1.0/d;
except
on E:Exception do
ShowMessage('Step4: 8087CW='+IntToStr(Get8087CW)+' d='+FloatToStr(d)+' '+E.Message+' Please mail me (cioina At hotmail.com) what kind of patch do you use?');
end;
 

Re:Re: New unofficial VisualCLX patch version 3.5 released

Hi,
in the meantime I tried to reproduce that myself, but it turned out to
be too cumbersome. I would have to install a SQL database (did that:
MySQL). At that point it appeared the MySQL version was too new and I
gave up.
BTW, it could be a hardware problem; actually I consider that probable.
Ever heard of the ominous VIA chipset related bug with systems>= 700
MHz? When the FPU raised an exception, the surprised user was greeted
by a fatal exception 0E blue screen.
See
groups.google.com/groups
Greetings, Robert
 

{smallsort}