> Well, I consider the problem as minor so I don't know if it's worth to
> introduce a new switch. I guess the best solution is to throw always a
> hint. Since 1/0=Inf is IEEE compliant, it's no real error. If people
> really want an error, they can create their own error msg file making
> the hint
Sasa Zeman wrote:
>> People will complain, if FPC isn't delphi compatible.
>
> FP actually is not 100% Delphi compatible by default mode and it is not
That's true.
> intention to be (regarding available informations on internet) it is
> actually intented to be compatible with Turbo/Borland Pasca
> People will complain, if FPC isn't delphi compatible.
FP actually is not 100% Delphi compatible by default mode and it is not
intention to be (regarding available informations on internet) it is
actually intented to be compatible with Turbo/Borland Pascal, I suppose.
Delphi simulation mode (-Sd,
Sasa Zeman wrote:
>> The program won't compile with -Cr.
>
> Program with -Cr will compile and link if all is correct. Eventually range
> check error compiler can predict, will stop compilation as usually.
> Otherwise, program itself will check range on each attemp to work with
> arrays or calcula
> Hello , I need to know whether someone has fast routines to calculate
> crc32 of let's say 64 k buffer.
> Any help would be appreciated
Almost all table oriented impelmentations using pointer arithmetic are fast
enough. You may be interested to take a look CRC32 unit on my site. It is
opera
> The program won't compile with -Cr.
Program with -Cr will compile and link if all is correct. Eventually range
check error compiler can predict, will stop compilation as usually.
Otherwise, program itself will check range on each attemp to work with
arrays or calculations, which is clearly waste
Hello , I need to know whether someone has fast routines to calculate
crc32 of let's say 64 k buffer.
Any help would be appreciated
Pianoman
- Original Message -
From: <[EMAIL PROTECTED]>
To:
Sent: Sunday, April 16, 2006 12:02 PM
Subject: fpc-pascal Digest, Vol 20, Issue 18
> Send fp
Sasa Zeman wrote:
>> We don't consider this as a bug, it's for delphi compatibility reasons.
>> These expressions are evaluated at compile time, so it's something
>> differnt. If you want to get an error, compile with -Cr.
>
> The -Cr will point on error in the code, however, enabling range checki
> We don't consider this as a bug, it's for delphi compatibility reasons.
> These expressions are evaluated at compile time, so it's something
> differnt. If you want to get an error, compile with -Cr.
The -Cr will point on error in the code, however, enabling range checking
will also affect on gl
Sasa Zeman wrote:
>>> FPC 2.0.2 do not rasie exception on integer/floats division by Zero,
> which
>>> is suitable for calucaltion I currently developing. Instead, division
>>> return infinity:
>>>
>>> writeln(1/0) -> +inf
>>> writeln(1.0/0) -> +inf
>> Already fixed.
>
> Unfortunatelly, bug still
> > FPC 2.0.2 do not rasie exception on integer/floats division by Zero,
which
> > is suitable for calucaltion I currently developing. Instead, division
> > return infinity:
> >
> > writeln(1/0) -> +inf
> > writeln(1.0/0) -> +inf
> Already fixed.
Unfortunatelly, bug still persists when division is
11 matches
Mail list logo
