I make rather heavy use of command line argument parsing. The Kix script engine displays the following as "it's own" arguments:
/D, /F, /R, /U, & /T
/R and /U require the format "arg:value"
There is a problem with this and using C/L arguments in scripts..
- Kix32 responds to "/" or "-" as arg specifiers, preventing the use of "-" args in scripts.
- Kix32 responds to /H, which is undocumented.
- Kix32 matches the first letter, so -DATA:val is interpreted as /D (debug).
I would like to see Kix be more strict in its argument matches, so that arguments can be passed to scripts without interference. Once change that would go a LONG way is to restrict Kix to using the "/" for its arguments, so that "-" can be used without conflict for script args.
I work around this now by using "+DATA", but the "+" is an unnatural argument initiator.
Glenn
_________________________
Actually I
am a Rocket Scientist!
