On 06/17/2015 10:29 PM, Paolo Bevilacqua wrote:
On Wed, Jun 17, 2015, at 04:43 PM, Damon Courtney wrote:
I think we’ve found your problem. More information is always better. :)
parray prints the array contents directly, it DOES NOT return a value.
So, if you’re logging this to a log file, you will see nothing from
parray.
If you want to see what’s in an array, use
puts $log [array get response]
Of course. I must have left brain in parking.
Interesting, load_response seems to keep adding data to the array, so
'unset' is needed before calling Will work on that.
Thanks Damon!
<i>Always striving to honor my word and commitments</i>
if you're running your script as a .tcl file then variables are created
by default in the global namespace, therefore they survive after a
request is processed. Moreover load_response was originally designed
(and modified) so that it behaved like the same command in NeoWebScript,
a Tcl based scripting environment that partially spurred the creation of
Rivet (Damon and David can be more accurate on this)
I suggest you read the code in rivet/rivet-tcl/load_response.tcl, it's
quite simple
now, what is the output once you fixed your test script?
-- Massimo
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
