Re: Service program / procedure design and naming conventions -- 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: Service program / procedure design and naming conventions
From: Dan <dan27649@xxxxxxxxx>
Date: Mon, 7 Aug 2017 12:14:29 -0400
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 \(AS/400 and 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/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On Fri, Aug 4, 2017 at 5:11 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

d PromptWindowOrg...
d pi 10a
d PromptWindowSubOrg...
d pi 10a

Are you familiar with the Don't Repeat Yourself principle in software
engineering? Have you considered writing a generic utility that displays a
window subfile that may contain code-value and description, and may display
data from any file in your database? Not only Org and Sub-Org, but ANY file
in your system?

I am familiar with the principle. I'm just not sure it can be (easily)
accomplished when Org has no key input parameter and SubOrg does. It goes
without saying that all of the different files will have different keys.
I'm not sure how that could be accomplished with one procedure.

- Dan

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Service program / procedure design and naming conventions , Dan

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.