Possible bug related to not interfacing overloaded functions
lazarus / 64-FPC development

----------------------------------------------------------------------
440bx · 2018-12-09 16:48

Hello,

When an overloaded function is interfaced, the compiler apparently
considers all the overloads to be interfaced even if they are not
explicitly and individually interfaced.

For instance, if you have two functions in a unit such as:
Code: Pascal  [Select][+][-]window.onload = function(){var x1 =
document.getElementById("main_content_section"); if (x1) { var x =
document.getElementsByClassName("geshi");for (var i = 0; i  function
Overloaded(constref parm1 : somerecord;                    const  
 parm2 : dword;                    const    parm3 : dword;           
       const    parm4 : dword) : boolean; and   function
Overloaded(constref parm1 : astruct;                    constref parm2
: astruct2) : boolean; 
Declaring the first one in the interface section makes the additional
overload also callable from outside the unit (that is not desirable.)

See attached for a complete, runnable, example.

----------------------------------------------------------------------
ASerge · 2018-12-09 17:13

Quote from: 440bx on December 09, 2018, 05:48:40 pmWhen an overloaded
function is interfaced, the compiler apparently considers all the
overloads to be interfaced even if they are not explicitly and
individually interfaced.
In the trunk version 3.3.1 already works correctly - compile time
error.

----------------------------------------------------------------------
440bx · 2018-12-09 17:31

Quote from: ASerge on December 09, 2018, 06:13:21 pmIn the trunk
version 3.3.1 already works correctly - compile time error.
Thank you Serge.  Nice to know it has already been fixed.  I'm looking
forward to the next stable release.

I should remember to always mention the compiler version.  Maybe
version 3.3.1 of my brain will remember these things.