declare global error

[Kenneth Brody]

On 11/7/2012 1:27 AM, Richard Kreiss wrote:
> On Nov 6, 2012, at 8:18 PM, "Dennis Malen" <dmalen at malen.com> wrote:
>
>> I am getting the following error:
>>
>> ERROR  Global 'sandy' already defined.
>>
>> I have a call statement in @entsel.
>>
>> In @entsel I have a "declare extern sandy"
>>
>> In the call statement I have "declare global sandy(8)"
>>
>> Any reason anyone can see why I would be getting an error.
>>
>> Sandy is not defined anywhere else in input processing.
[...]
> Try reversing the declare. Put declare global in the calling process and
> declare external in the called program.

See my other e-mail as to *why* this might be a solution.

> Another solution, if you gave an auto process table is declare global
> there.  Then sandy will be available in any processing table.

Declared variables do not "share" between processes based on whether or not 
they're declared in automatic processing, as is done with dummy fields.  The 
"sharing" is done entirely on whether you use "declare global" or "declare 
local".

-- 
Kenneth Brody