What has happened?

[Brian K. White]

----- Original Message ----- 
From: "Kenneth Brody" <kenbrody at bestweb.net>
To: "Brian K. White" <brian at aljex.com>
Cc: "filePro mailing list" <filepro-list at seaslug.org>
Sent: Tuesday, September 27, 2005 3:47 PM
Subject: Re: What has happened?


> Quoting Brian K. White (Tue, 27 Sep 2005 15:21:28 -0400):
> [...]
>> They use a lot of the same long variables, but some lengths and edits
>> changed in the new one.
>>
>> What would work best for me I think is if I can just insert a line at
>> the top of the old table that looks at a variable and decides to chain
>> to the new table.
> [...]
>> Also, it just occured to me I might have the same problem with the
>> conflicting variable definitions even if it worked like 1), because the
>> declares are read before any code is run, including the goto or chain
>> I'd have at the top.
>
> All variables are determined at compile time (dclerk/dreport/rcabe) or
> at load time (rclerk/rreport), before any code is run.  As such, any
> DECLAREd variables will be created prior to any code in that table
> being executed.

What does that clarify about the question of what will be my env in the 
table I chained to?

Posit: Both tables have their own overlapping sets of declares. At the top 
of table 1, I chain to table 2.

Are the declares from table 1 still in effect, making the declares in table 
2 become conflicts? (reasonable, I never left clerk and I'm chaining not 
calling)
Or does the new table start with a clean slate in that regard? (reasonable, 
I loaded a new table, and call works this way.)

Also note I'm not talking about the possible conflicts with mismatched 
global and extern declares. There is no amiguity what needs to be done 
there.
Just local declares that are the same name & basic function but not the same 
definition.

Brian K. White  --  brian at aljex.com  --  http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!