All:
To summarize what Eric has said, treat "the result" much as you would
"it". It's hard to be sure what else might change the value stored in
it if you don't either save its value to another var for later use,
or use it immediately after you've acquired it. Actually, this is
more for me as a method of reinforcing my memory. Most already are
aware of this caveat.
Joe Wilkins
On Jan 20, 2008, at 2:17 AM, Eric Chatonet wrote:
Hi Steve,
In order to get a reliable value in the result function, the result
*must* be tested immediately after the command:
save this stack
if the result <> empty then...
No code between these two lines. Never.
If you need it, you may write:
save this stack
put the result into tResult
<additional code>
if tResult <> empty then...
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
