RE: visibility of file fields

The two things that threw me off were using the global field name in the
data structure in the way I'm used to doing in a main program, and that the
fields in question were file fields rather than variables defined in the D
specs of the global section of the source.  I don't object to the way it
works and I understand the idea of the scope of automatic variables.  I
think you could argue that a data structure subfield in a D spec that
doesn't "define" the variable (explicitly mention type and size) ought to be
the global of the same name if one exists.  Whether it's easy or sensible to
do that is a different question.

> -----Original Message-----
> From: Scott Mildenberger [mailto:Smildenber@Washcorp.com]
> Sent: Thursday, March 28, 2002 6:44 AM
> To: 'midrange-l@midrange.com'
> Subject: RE: visibility of file fields
>
>
> Joel,
>
> When you have a local and global field (all file fields are
> global) with the
> same name, they are in fact two different fields.  And within the
> subprocedure the local field will 'hide' the global one which
> means you
> cannot access the global field within the subprocedure.
>
> Scott Mildenberger
>