- One of the most obvious examples of this is an object loop. I usually use 'vValue', expecting a string/number, but it could be an object.
Code: Select all
for vKey, vValue in oArray vOutput .= vKey " " vValue "`r`n"
- Some possibilities. None are great.
- Has anyone else had this problem, or come across/considered a solution? Cheers.
- [EDIT:] A related point. I have a function that can accept an hMenu or an hWnd, based on the options parameter.
- Possibilities. Again, not great.
- [EDIT:] Also related. An array of structs. E.g. MCM_GETSELRANGE requires a struct that is two SYSTEMTIME structures back-to-back. If I have one SYSTEMTIME structure, I called the variable SYSTEMTIME. But what about multiple SYSTEMTIME structures.
- A possibility. So-so.
[EDIT:] or arrSYSTEMTIME
- Note: I don't use prefixes with struct names, or constants, but I'm tempted to, because prefixes to indicate variable or object always make things easier.
- Note: In this context the word 'array' is used, but it is what I would usually call a 'variable' (text/string/binary data), and not an 'object' (array/COM object).