Declare global in called table goes away following lookup?

[Kenneth Brody]

Quoting Barry Wiseman (Sun, 19 Aug 2007 16:02:34 -0400):

>
> Linux dclerk 5.0.14D4 (I know, I know)
>
> My variable is a declare global in the called table, a declare extern in the
> main table.  I am loading the variable in the main table, then doing  
>  the call.
> All is well until the called code performs a lookup, following which the
> variable has become blank.   The following test code demonstrates   
> the problem:
[..]
> This behavior occurs only when the lookup is back to the file the   
> main table is
> standing on, and is not affected by whether the lookup succeeded or failed.
[...]

 From the 5.0.15 readme:

(All) #783

     A non-dash lookup to the main file may clear non-",g" DECLAREd
     variables.  (See also #785.)

(All) #785

     If you have DECLAREd GLOBAL variables in the automatic and/or the
     input/output table, and then CALL another table which DECLAREs
     addtional GLOBAL variables, such that the total number of such
     variables crosses a multiple-of-32 boundary, and then from within
     the main input/output table execute a non-dash lookup to the main
     file, filePro may crash.  (See also #783.)

-- 
KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
http://www.hvcomputer.com
http://www.fileProPlus.com