variables losing value on current file aliased lookup

[Bruce Easton]

(top post)

Thanks Ken and other responders - i was just getting ready to try
with a ,g just for curiosity's sake.  I guess I hadn't run into this 
before,
because generally I don't use a "stand on to run" type file to hold
control or any other data.

Bruce

Bruce Easton
STN, Inc.


On 4/20/10 12:43 PM, Kenneth Brody wrote:
> On 4/20/2010 11:18 AM, Bruce Easton wrote:
>> Below I show some code along with comments below that to explain some
>> unexpected runtime results.     (filepro 5.0.14 - Linux)
>> The code is invoked with clerk from the file "control".
> [...]
>>            Then: declare GLOBAL targdir(20,*)
> [...]
> [...]
>> The debugger shows that the value of "targdir" is retained until line
>> 150, and
>> that as soon as the lookup on line 150 is executed (successfully) the
>> values of
>> "tardir", and other variables, are cleared.    I don't usually use a
> [...]
>> Is this behavior expected?
>
> This was fixed long ago.
>
> Quoting the 5.0.15 and 5.6 beta readme files:
>
> (All) #783
>
>     A non-dash lookup to the main file may clear non-",g" DECLAREd
>     variables.  (See also #785.)
>