Currently, kix32.exe only accepts variables in the format of $var="blah", a few predefined switches, and/or additional script names as arguments. If you try to provide any other type of argument, it causes an error.
With the current addition of the getcommandline() function, I would like to suggest adding another switch to kix32.exe that would allow you to use your own structure for arguments. For example:
Code:
kix32 /o script.kix [Open/Other arguments]
Once the /o switch is set to kix32.exe, it would allow the user to define variables in the format they choose, and they would have to handle the variables in the code via the getcommandline() function.
In the mean time I did find a workaround that would allow some degree of open arguments, but it requires that the script end with "Quit" to keep it from trying to run the arguments as scripts. For example:
kix32 script.kix 1234567890 abc edf
Code:
break on
for each $arg in getcommandline(1)
? $arg
next
quit 0
Returns:
Quote:
kix32
script.kix
1234567890
abc
edf
