Currently, Round and Trunc functions ignore the state of $OVERFLOWCHECKS
compiler directive. The following code prints -2 -2:
{$MODE OBJFPC}{$OVERFLOWCHECKS ON}
var
a: Integer;
b: Double;
begin
b := MaxInt;
a := Round(2.0 * b);
Writeln(a);
a := Trunc(2.0 * b);
Writeln(a);
end.
This
Alexander Klenin schrieb:
Currently, Round and Trunc functions ignore the state of $OVERFLOWCHECKS
compiler directive. The following code prints -2 -2:
{$MODE OBJFPC}{$OVERFLOWCHECKS ON}
var
a: Integer;
b: Double;
begin
b := MaxInt;
a := Round(2.0 * b);
Writeln(a);
a :=
On 13 Jun 2009, at 13:31, Alexander Klenin wrote:
Currently, Round and Trunc functions ignore the state of
$OVERFLOWCHECKS
compiler directive. The following code prints -2 -2:
{$MODE OBJFPC}{$OVERFLOWCHECKS ON}
var
a: Integer;
b: Double;
begin
b := MaxInt;
a := Round(2.0 * b);
On Sat, Jun 13, 2009 at 22:47, Jonas Maebejonas.ma...@elis.ugent.be wrote:
On 13 Jun 2009, at 13:31, Alexander Klenin wrote:
Currently, Round and Trunc functions ignore the state of $OVERFLOWCHECKS
compiler directive. The following code prints -2 -2:
In Borland-speak, these are not overflow
On 12 Jun 2009 at 16:56, Florian Klaempfl wrote:
See the DirectPutpixel call in graph.inc line 848:
{ x1 mod 8 }
if RevBitArray[x1 and 7] and TmpFillPattern 0 then
DirectPutpixel(x1,y)
else
Imo
On 13 Jun 2009, at 14:27, Alexander Klenin wrote:
On Sat, Jun 13, 2009 at 22:47, Jonas
Maebejonas.ma...@elis.ugent.be wrote:
The difference between range and overflow errors is as follows:
* range errors occur when an implicit type conversion occurs from
one type
to another (e.g., when
