[EMAIL PROTECTED] wrote:
bug 3626 is marked as Not a bug. This is wrong! The comment is also
wrong!
Why? 9 is a valid int64...
Vincent.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
[EMAIL PROTECTED] wrote:
int64 integer ???
The compiler reports a range check error depending on $R as warning or error. So
where is the problem? What do you expect to happen?
Vincent Snijders wrote:
[EMAIL PROTECTED] wrote:
bug 3626 is marked as Not a bug. This is wrong! The comment is also
On 2 feb 2005, at 16:43, [EMAIL PROTECTED] wrote:
int64 integer ???
They are assignment-compatible. If the value doesn't fit in the range
of the destination type, you get either a warning (if range checking is
off) or an error (if range checking is on).
Jonas
I expect a out of bounds error messeage. Independent from $R.
Florian Klaempfl wrote:
[EMAIL PROTECTED] wrote:
int64 integer ???
The compiler reports a range check error depending on $R as warning or
error. So where is the problem? What do you expect to happen?
Vincent Snijders wrote:
[EMAIL
[EMAIL PROTECTED] wrote:
int64 integer ???
The compiler reports a range check error depending on $R as
warning or error. So
where is the problem? What do you expect to happen?
im not going to argue whether this is right or wrong but in delphi at least
$R only affects run time range
[EMAIL PROTECTED] wrote:
int64 integer ???
The compiler reports a range check error depending on $R as
warning or error. So
where is the problem? What do you expect to happen?
If I got it right the question is about a comparison statement of two
integer numbers. IMHO from the logocal view this
As you can see there's nothing really serious, I can contribute code if
you tell me.
I hope IO will be useful to fpc and lazarus projects.
I'm sure it will be. Feel free to send patches to me for anything you
think needs fixing.
Ok, now I'll download fpc from cvs and I'll create some
On Tuesday 01 February 2005 10:11, Marco van de Voort wrote:
On Tue, 1 Feb 2005 [EMAIL PROTECTED] wrote:
Classes:
1 - fpc lacks a HexToBin and BinToHex functions. [It has them but only
as private methods of TParser]
These functions are in sysutils or strutils. They have no place in
can agree.
peter green wrote:
im not going to argue whether this is right or wrong but in delphi at least
$R only affects run time range checking. In delphi that code will give an
error (constant expression violates subrange bounds) even with range
checking off.
im not going to argue whether this is right or wrong but in delphi at
least
$R only affects run time range checking. In delphi that code will give
an
error (constant expression violates subrange bounds) even with range
checking off.
I think this is a special case with for-loops. Delphi also
10 matches
Mail list logo
