Dear Shawn,
You are right. Manytimes we see all kind of code which aren't strictly confirm
Ruud's documentation.
it
- may introduce unknown errors.
- may return all kind of compatibilities problems during upgrading to new release.
Some examples of not strictly code
- SetOption(DisableDebugging,off)
instead of
SetOption("DisableDebugging","off") - Shell 'cmd /c setup.exe '
instead of
Shell '%comspec% /c setup.exe - ? "Info: @userid - @wksta - $message"
instead of
? "Info: "+@userid+" - "+@wksta+" - "+$message
With the tools "kixref" and "kixstrip" we try to verify the correctness of
scripts. In some situations these tools are more correct than kixtart (f.e.
WHILE/LOOP endless loop situation by missing LOOP statement).
In some situations Ruud can't cover "bad" code. Normally it may not work, but
it did. A nice example in the past was the way "how DIM command in Kixtart
3.6x releases was working". Ruud introduces REDIM as workaround.
greetings.
