Currently when you call a method in Xojo the parameters are matched up starting from the first to the last from left to right. They are matched up based on their position in the argument list.<\/p>\n\n\n\n
One thing some other languages support is “named parameters”.<\/p>\n\n\n\n
What this allows is a certain degree of flexibility that doesn’t exist with positional parameters like Xojo uses.<\/p>\n\n\n\n
For instance in Xojo if you have a method, Foo, with parameters as follows<\/p>\n\n\n\n
Sub Foo(a as integer, b as string, c as Date)<\/code><\/pre>\n\n\n\nyou can call it only using the correct types of parameters in the correct order like<\/p>\n\n\n\n
Foo(123, \"345\", new Date)<\/code><\/pre>\n\n\n\nThere are ways, with optional parameters, to modify this normal operations. If that method was defined as<\/p>\n\n\n\n
Sub Foo(a as integer = -1, b as string = \"\", c as Date = nil)<\/code><\/pre>\n\n\n\nYou could call this like<\/p>\n\n\n\n
Foo()\nFoo(123)\nFoo(123, \"345\")\nFoo(123, \"345\", new Date)<\/code><\/pre>\n\n\n\nAll the parameters are optional and any that are not supplied a default value as shown in the declaration. But everything is still positional. And there are things you cannot do like skip one parameter. None of these will compile.<\/p>\n\n\n\n
\nFoo(, ,New Date)\nFoo( , \"345\" ,New Date)\nFoo(123, ,New Date)<\/code><\/pre>\n\n\n\nSo how would named parameters help ? Named parameters can let you say, explicitly, “this value is for this parameter” rather than just matching up by position. For instance out call to Foo might look like <\/p>\n\n\n\n
Foo()\nFoo( a:123)\nFoo( a:123, b:\"345\")\nFoo( a:123, b:\"345\", c:new Date)<\/code><\/pre>\n\n\n\nAnd you might also be able to do something like<\/p>\n\n\n\n
Foo( b:\"345\", a:123 )\nFoo( a:123, c:new Date, b:\"345\")<\/code><\/pre>\n\n\n\nAnd not have to worry about the order. And this might let you do something like<\/p>\n\n\n\n
Foo(c:New Date)\nFoo( b:\"345\" , c:New Date)\nFoo(a:123, c:New Date)<\/code><\/pre>\n\n\n\nwhich skips certain parameters in a manner that you cannot do today.<\/p>\n\n\n\n
Certainly this would not be a trivial change to Xojo to support positional and\/or named parameters. But there are languages that do this.<\/p>\n\n\n\n
In the mean time its possible to manually create your own support for “named parameters”. <\/p>\n\n\n\n
If we create Foo with two signatures like <\/p>\n\n\n\n
Sub Foo(a as integer = -1, b as string = \"\", c as Date = nil)\nEnd Sub\nSub Foo(paramarray values as Pair)\nEnd Sub<\/code><\/pre>\n\n\n\nThen Foo could be called as<\/p>\n\n\n\n
Foo(123, \"345\")\nFoo(123, \"345\", New Date)\nFoo( \"c\":New Date)\nFoo( \"b\":\"345\" , \"c\":New Date)\nFoo( \"a\":123, \"c\":New Date)<\/code><\/pre>\n\n\n\nNOTE that the “names” of the parameters have to be a literal type – in this case a string. <\/p>\n\n\n\n
In this set up though we cant use no parameters. So let’s alter the set up to have at least one parameter otherwise the compiler will have an ambiguous overload in the case there are no parameters. It couldn’t distinguish between the call to Foo where it should use all default parameters and an empty paramarray. So now our declarations look like<\/p>\n\n\n\n
Sub Foo(a as integer = -1, b as string = \"\", c as Date = nil)\nEnd Sub\nSub Foo(value as pair, paramarray values as Pair)\nEnd Sub<\/code><\/pre>\n\n\n\nAnd we’ll be able to call this like<\/p>\n\n\n\n
\/\/ these are positional\nFoo\nFoo(123)\nFoo(123, \"345\")\nFoo(123, \"345\", New Date)\n\n\/\/ the use \"named\" parameters\nFoo( \"c\":New Date)\nFoo( \"b\":\"345\" , \"c\":New Date)\nFoo( \"a\":123, \"c\":New Date)<\/code><\/pre>\n\n\n\nSo we’re on our way to being able to use either positional parameters OR named parameters. Now how do we make use of the overload that supports named parameters to call the one that supports positional parameters ?<\/p>\n\n\n\n
In this method we need to<\/p>\n\n\n\n
- make sure we declare one local variable of the same type for each positional parameter<\/li>
- make sure we set these local variables default value to the same default values as the version that uses positional parameters<\/li>
- process the FIRST pair and all subsequent pairs in the same fashion and assign values to the local variables<\/li><\/ul>\n\n\n\n
Following all those admonitions the code in the version of foo using named parameters looks like <\/p>\n\n\n\n
Dim a As Integer = -1\nDim b As String \nDim c As Date\n\nSelect Case value.Left\nCase \"a\"\n a = value.Right.IntegerValue\nCase \"b\"\n b = value.Right.StringValue\nCase \"c\"\n c = value.Right\nEnd Select\n\nFor i As Integer = 0 To values.ubound\n \n Select Case values(i).Left\n Case \"a\"\n a = values(i).Right.IntegerValue\n Case \"b\"\n b = values(i).Right.StringValue\n Case \"c\"\n c = values(i).Right\n End Select\n \nNext\n\nfoo(a, b, c)\n<\/code><\/pre>\n\n\n\nThere are caveats to this technique though. Positional parameters will be checked by the compiler for type, the “named parameter” version will only be checked that the passed items ARE pairs. The names and values contained by those pairs are variants and so can be anything. And you can pass the same named parameter multiple times since the compiler is unaware of named parameters. And you can’t use “byref” parameters with the named parameter version – you COULD use reference types though.<\/p>\n\n\n\n
I’d love to see Xojo support named and positional parameters using a syntax that looks like “pairs” as first presented.<\/p>\n\n\n\n
In the mean time this is what we have.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Currently when you call a method in Xojo the parameters are matched up starting from the first to the last from left to right. They are matched up based on their position in the argument list. One thing some other languages support is “named parameters”. What this allows is a certain degree of flexibility that … <\/p>\n