I noticed this piece of code works just fine the first time though
Sub Main
/declare somevalue int outer
/varset somevalue 99
/if (${somevalue}>0) /echo Outer is more then 0
/endmacro
/return
But on the second it's producing an error saying /declare failed. Unless I type in /zapvars. I added teh /endmacro line in there after reading the descripting of zapvars and the line about /endmacro calling it directly. It doesnt' change though. I have to use a /zapvars manually ( or as the first line of my script ) to clear them.
/zapvars
Usage: /zapvars
This takes no parameters, just zaps all OUTER scope variables. /endmacro does this no
matter what, so I might just remove this command altogether. There is no "array" scope
or "timer" scope to tell it to keep.
Also... Since we could pass parms into a function with the following defination...
Sub SomeFunc( p0 , p1 )
Now Should we not be able to use this? ( Yea , I know string is redundent there, Its jsut an example )
Sub SomeFunc( p0 string , p1 string )
I find that If I use the latter, when I pass in 2 arguments, and then test them / try to print them.. I get a value for p0, but p1 would be null everytime. I'm assuming it's making another variable named string in that case as var #2, and then creating a 3rd and 4th
Nothing up there is detremental. Just some little quirks I noticed, which are easily bypassed for now.[/u]

