I was looking for a good excuse to post this observation ... not sure if this is a known bug in KiX32 for Windows NT or not ...

Try the following script at your own risk. Kiddies - don't try this at home unless you have parental supervision ...

Sample script called "echo.kix" ...

--- 8< ---
break on
?'The value of $$var is "$var"'
exit
--- 8< ---

Call it from the command line like this...

kix32 echo.kix $var="hello world"

you get ...

The value of $var is "hello world"

Easy-peesie eh ?

Now - call it like this ...

kix32 echo.kix $var

KiX32 spins off into an infinite loop (ala 100% CPU land) and generally barfs like it just ate a bad tuna sandwich !

Another example for ALWAYS putting a "BREAK ON" statement in all your scripts ( at least until it's ready for production ).

Shawn.

[This message has been edited by Shawn (edited 15 May 2000).]