RE: Constants in RPG -- 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: Constants in RPG
From: Kurt Anderson <kurt.anderson@xxxxxxxxxxxxxx>
Date: Fri, 3 Apr 2009 08:50:53 -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 IBM i / System i <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>

On Behalf Of Charles Wilt
"Unlike variables, there's no benefit to declaring a constant locally."

Systematically, correct. However when it comes to grouping code logically, I will put a constant into a subprocedure. The benefit is, if at all possible, to keep everything involved in a procedure within that procedure. Ease of portability (say, from a program into a service program). Also ease of use (I can shift my eyes upward to see the value of the constant if I so need - in WDSC anyway).

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.