declare global error

[Kenneth Brody]

On 11/7/2012 6:05 PM, Dennis Malen wrote:
> Here are my results:
>
> I don't understand why, but (as suggested) by reversing the "global" and the
> "extern" fixed the error that was popping up.

I explained why in my previous e-mail:

>> Are you assigning a value to "sandy" in input processing prior to calling
>> the processing with the "declare global"?  If so, that's the problem, and
>> you'll need to put the "declare global" in the input processing.
>>
>> filePro will allow you to make the assignment to a variable that, so far,
>> has only been declared "extern", and gives it a tentative definition based
>> on that value.  However, unless the value assigned to it matches the
>> definition in the eventual "declare global", the tentative definition and
>> the "real" definition in the "declare global" won't match, and you'll get
>> the above error.  (So, in the above instance, if you were to assign an
>> 8-character value to sandy, you wouldn't get the error.  However, you'd only
>> be hiding the fact that there is a problem.)

[...]

-- 
Kenneth Brody