On 28 Mar, Stewart Allen wrote:
>> I've also found that the global variables are initilized to a real
>> value, not a result. So even if I manually modify the generated script
>> to get:
>>
>> global foo; set foo [bar]
>>
>> when I load and save with vtcl, the result is
>>
>> global foo; set foo {foobar}
>>
>> where {foobar} is whatever value was originally returned by bar.
>
> This is an artifact of "sourcing" a file. You should set these
> values inside of a procedure which you call.
>
Yes, that's what I wanted to do but because the value was initialized
in the global procedure, I had to try to work around it. With the
option to be added in the next version, the problem should go away.
Any idea on when 1.09 will be out?
--
Laurent Duperval, Systems Analyst Grafnetix Systems Inc.
Tel: (514) 861-3389 777, de la Commune Ouest
Fax: (514) 866-6206 Suite 101, Montreal, Qc
[EMAIL PROTECTED] Canada, H3C 1Y1
URL: http://www.Grafnetix.COM/
Personal URL: http://www.Grafnetix.COM/~laurent/
