rpg400-l-digest V1 #200

[bmorris@xxxxxxxxxx]

>Date: Wed, 25 Aug 1999 23:55:31 EDT
>From: SirZetar@aol.com
>Subject: Re: Constant Scope - Comments
>
>What I hadn't noticed before was that even tho the compiler didn't like the
>constants in the D specs of the procedure, it had no problem with them in the
>C specs of that same procedure.

Ok, now I understand.  Here's a little module with the problem:

H nomain
D globconst       c                   1
D proc            pr
p proc            b
D arr             s              1a   dim(globconst)
p proc            e

The compiler requires that constants for DIM and OCCURS be already defined on
the
array or mds statement.  It can't tell whether there's going to be a local
version
of that name.  If the compiler accepted the global constant for DIM or OCCUR, it
would have to count that name as "defined" for the subprocedure (basically
create a
local definition the same as the global definition).  This behaviour would be
too
capricious, in my opinion.

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---