El 05/12/18 a las 08:46, Jonas Maebe escribió:
On 05/12/18 07:51, LacaK wrote:
helps, but why is it not needed in Win32? Why for Win32
"integer"-"integer" is considered as "integer" so compiler can determine
which overloaded function to call and for Win64 compiler compiler can
NOT determine whic
>> helps, but why is it not needed in Win32? Why for Win32
>> "integer"-"integer" is considered as "integer" so compiler can determine
>> which overloaded function to call and for Win64 compiler compiler can
>> NOT determine which overloaded function to call?
>
> It is because as documented at
> h
On 05/12/18 07:51, LacaK wrote:
helps, but why is it not needed in Win32? Why for Win32
"integer"-"integer" is considered as "integer" so compiler can determine
which overloaded function to call and for Win64 compiler compiler can
NOT determine which overloaded function to call?
It is because a
>
>> Hi *,
>>
>> this code compiles for target Win32 but does not compile for
>> Win64/x86-64. Why? Is there workaround?
>> (Error: Can't determine which overloaded function to call)
>> Thank you
> For me, in win32 works fine
Yes in Win32 works also for me. And this is my question why it does wor
El 04/12/18 a las 13:21, LacaK escribió:
Hi *,
this code compiles for target Win32 but does not compile for
Win64/x86-64. Why? Is there workaround?
(Error: Can't determine which overloaded function to call)
Thank you
For me, in win32 works fine
try this
r1.Offset(a-Integer(1),b-Integer(1));
Hi *,
this code compiles for target Win32 but does not compile for
Win64/x86-64. Why? Is there workaround?
(Error: Can't determine which overloaded function to call)
Thank you
-Laco.
=== code sample ===
TRec1 = record
x,y: integer;
function Offset(const Ax,Ay: integer): TRec1; overload
