What is the point of the key "Default" if it have 0 effect?

[Guest]

 

This

Test(Default)

Func Test($var = 10)
    ConsoleWrite($var & @CRLF)
EndFunc

 

Will print "Default" and not 10.

Due to this, There is no any logic why make it look "special". Unless it will realy actually prints 10 without any additional code.

Otherwise it's just like any regular string.

Why you did not make it so it will naturally get the Default value?

Edited February 19, 2017 by Guest

[Melba23]

gil900,

Of course it prints "10" - there is a big difference between the Default keyword as a parameter and a default parameter in a function definition.

The Default keyword as a parameter tells the function that the user wishes the parameter to use whatever the function defines internally as a default value, which must be set programmatically within the function. A default parameter in a function definition tells the function what to use if that parameter is omitted when the function is called. So in the example you give, the parameter is set to Default keyword - and that is what the function receives to do with as it sees fit. If you omit the parameter when calling the function it will use the default value for that parameter which is defined as 10.

To me the difference between these two behaviours is so obvious that I am struggling to see how it can possibly be unclear to others.

M23

[spudw2k]

Agreed.  As per the help file,
" When used in parameter passing, the behavior is specified in the corresponding AutoIt function documentation.
For UDF's, it is the scripter's responsibility to check if the parameter has been set to Default and to perform the desired behavior in this situation.
If used, the passed parameter will be set to the Default keyword and not to an optional parameter value, if defined. "