hi,

> you could also provide a logging object in the binding (e.g. an
> org.slf4j.Logger) to examine the script's state during execution.

that sounds good, although i don't know that i fully grok what you mean.

ideally the scripts would not be re-written to do extra logging in the
Groovy code manually, it would be more of an invasive snapshot
logging, or it would be Groovy logging whenever a variable's value is
updated.

is the latter what you mean, or how might one do the latter?

thanks!

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

  http://xircles.codehaus.org/manage_email