Killzone kid – User talk
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) |
Lou Montana (talk | contribs) mNo edit summary |
||
| Line 7: | Line 7: | ||
:Say you want an array: myArray[] = {1,2,3}; You write getMissionConfigValue [myArray, []], right? So no param, you guaranteed to get empty array. But user can write myArray = 123; and you will get 123 instead of array and script error. This is what I mean by you cannot enforce type so that it will return array no matter what. [[User:killzone_kid|killzone_kid]] ([[User talk:killzone_kid|talk]]) 14:13, 10 September 2019 (CEST) | :Say you want an array: myArray[] = {1,2,3}; You write getMissionConfigValue [myArray, []], right? So no param, you guaranteed to get empty array. But user can write myArray = 123; and you will get 123 instead of array and script error. This is what I mean by you cannot enforce type so that it will return array no matter what. [[User:killzone_kid|killzone_kid]] ([[User talk:killzone_kid|talk]]) 14:13, 10 September 2019 (CEST) | ||
Thanks for the precision; indeed no type can be "forced". To me a parallel can be made with [[getVariable]]'s alternative value's behaviour… maybe a common note should be thought of, along the line "value can be of any type, default value is not related to the current value type".<br> | |||
On a side note, did you get a Wiki notification for this/these message/s? - [[User:Lou Montana|Lou Montana]] ([[User talk:Lou Montana|talk]]) 14:24, 10 September 2019 (CEST) | |||
Revision as of 14:24, 10 September 2019
getMissionConfigValue note
Hello, I admit I didn't understand your note there:
I think it is confusing as no command can "force" any type, why this specific note on this specific command? - Lou Montana (talk) 13:55, 10 September 2019 (CEST)
- Say you want an array: myArray[] = {1,2,3}; You write getMissionConfigValue [myArray, []], right? So no param, you guaranteed to get empty array. But user can write myArray = 123; and you will get 123 instead of array and script error. This is what I mean by you cannot enforce type so that it will return array no matter what. killzone_kid (talk) 14:13, 10 September 2019 (CEST)
Thanks for the precision; indeed no type can be "forced". To me a parallel can be made with getVariable's alternative value's behaviour… maybe a common note should be thought of, along the line "value can be of any type, default value is not related to the current value type".
On a side note, did you get a Wiki notification for this/these message/s? - Lou Montana (talk) 14:24, 10 September 2019 (CEST)