Re: Scoping of procedure-level variables -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Scoping of procedure-level variables
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Wed, 02 Jul 2008 13:11:05 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the AS400 / iSeries <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Wilt, Charles wrote:

I don't think so Joe.

With or without the STATIC keyword on a RPG local procedure variable, the scope (or visibility)
remains the same; It can only be accessed within that procedure.

Yup. You and Adam are right. Dynamic scoping is a concept that basically I don't even understand. I'm reading more, but at first reading, I can't believe that RPG can be anything other than static (lexical) from a scope standpoint.

Joe

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Scoping of procedure-level variables , Joe Pluta

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.