You didn't read or understand what I have wrote, I'm afraid.
What is "analyzed to death" 20+ years ago? How involving uint64 will cause problems?
Same, but 32-bit case, before int64-on-32-bit introduction. As said, initially D3 was released with a
31-bit unsigned integer. (see e.g.
http://www.ebob42.eu/delphi4/language.htm )
Even GCC derivate GNU Pascal did something similar for a while that makes clear the issues involved are not fanta, since these three (Delphi, FPC, GPC) are codebases independent of each other (see
https://www.gnu-pascal.de/gpc/Cardinal.html)
Don't be theatrical,
I'm not. I name easy verifiable facts. For your convenience I added some links above.
please and write when uint64 in introduced by Delphi and when with FPC as native type.
I don't know about Delphi, I think XE2, since adding 64-bit triggered a major compiler revamp. FPC was earlier, 2.2 or 2.4.
AFAIK, that happens few years ago and as such is hardly "analyezed to death". I bet it was introduced in FPC without any deeper though about.
Bet based on what? I've already mentioned the cardinal->longword migration of Delphi in the early 2000s several times.
But yes, it was introduced while it was known to be flawed. The reasoning is that it would be better to directly translate structures (e.g. winapi) to it using the correct types, and increasing 64-bit activity made that come closer, and if you didn't mix types it would be ok. (e.g. a type that is a file offset).
Keep in mind that even e.g. 64-bit file offsets are signed, on both Unix and Windows.