On 04/04/12 12:23, Jonas Maebe wrote:
Paul Ishenin wrote on Wed, 04 Apr 2012:
04.04.2012 17:08, kyan ???:
Delphi doesn't support qword at all, so there is no Delphi
behaviour to
be compatible with in that case. Or at least it didn't when the above
was implemented. Does it now?
No, it d
Paul Ishenin wrote on Wed, 04 Apr 2012:
04.04.2012 17:08, kyan ???:
Delphi doesn't support qword at all, so there is no Delphi behaviour to
be compatible with in that case. Or at least it didn't when the above
was implemented. Does it now?
No, it does not.
Delphi XE has a UInt64 type.
04.04.2012 17:08, kyan написал:
Delphi doesn't support qword at all, so there is no Delphi behaviour to
be compatible with in that case. Or at least it didn't when the above
was implemented. Does it now?
No, it does not.
Delphi XE has a UInt64 type. From the documentation:
UInt64 represents
>> Delphi doesn't support qword at all, so there is no Delphi behaviour to
>> be compatible with in that case. Or at least it didn't when the above
>> was implemented. Does it now?
>
>
> No, it does not.
Delphi XE has a UInt64 type. From the documentation:
UInt64 represents a subset of the whole
04.04.2012 16:34, Jonas Maebe wrote:
Delphi doesn't support qword at all, so there is no Delphi behaviour to
be compatible with in that case. Or at least it didn't when the above
was implemented. Does it now?
No, it does not.
Best regards,
Paul Ishenin
___
patspiper wrote on Wed, 04 Apr 2012:
In contrast, FPC's TVarRec can hold integer, Int64, and qword,
meaning that a qword is passed as a qword and not Int64. So since
FPC's TVarRec includes qword while Delphi's does not, why not add
dword as well?
Delphi doesn't support qword at all, so th
On 04/04/12 01:57, Jonas Maebe wrote:
On 03 Apr 2012, at 20:27, patspiper wrote:
The following is related to bug #0021641 (Array of const gives check range
error).
Is it correct for the exception to manifest itself in the dword case and not
the qword one?
writeln(Format('%d', [qword(qword
