I havent succeeded in doing that. I find it very frustrating that the
overload stuff does not distinguish between integer and int64. It
doesnt work for float and datetime either. I have ended up having
prefixes for the data type.
On 21/09/2010 11:08, John Bird wrote:
Quite a few built in
I had a friend who wrote a bignums unit for turbo pascal (5.5 I
believe) when we were at school which could handle really really big
numbers. His poor old XT took awhile to calculate some of these crazy
numbers. There will likely be various libraries that you can use.
Alister Christie
Compu
> eg 17! (17Factorial) is the highest I can get exactly (17*16*15 etc.),
> 18! turns to a real number and I don't know if I am losing digits.
So: mathematical curiosity - cool. :)
> Another example of large numbers is time converted to milliseconds:
>
>Thisint64:=strtoint(formatDateTime(
I have a calculator program, beyond certain size numbers it resorts to real
numbers, when sometimes I want exact integers.
eg 17! (17Factorial) is the highest I can get exactly (17*16*15 etc.), 18!
turns to a real number and I don't know if I am losing digits.
Another example of large numbers
Behalf Of John Bird
Sent: Tuesday, 21 September 2010 11:08
To: NZ Borland Developers Group - Delphi List
Subject: [DUG] integer or int64
Quite a few built in Delphi functions accept either integer or int64 as an
argument, I checked into inttostr for instance, in that case its asm code.
I have
Quite a few built in Delphi functions accept either integer or int64 as an
argument, I checked into inttostr for instance, in that case its asm code.
I have quite a few standard number processing routines, and up to now have
done one version for integer, and another for int64.
Is it feasible to
