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 11:09:14 -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>

David Gibbs wrote:

Pardon my denseness here ... but what does 'lexical' mean in this context?

Another word for static. I pretty much always use static.

And the answer is "it depends" <grin>. If you specify the word STATIC on a variable in a procedure, it is indeed static.

However, there is now an additional wrinkle added with the multithreading capabilities of 6.1 (yes, I'm trying to use the new naming conventions for the OS as well), as to whether the scope of a static variable is across threads or not.

Joe

As an Amazon Associate we earn from qualifying purchases.

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.