Re: Maintaining Service Program signatures -- RPG400-L

Subject: Re: Maintaining Service Program signatures
From: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
Date: Wed, 20 Feb 2013 08:50:46 -0800
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/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 2/19/13 6:26 PM, aec wrote:

For a long time I always copied my list of procedures every time I added
one, and used the *Previous *Current signatures for changes, but then
learned that you could keep the same signature if you did it right.
Saved me a lot of repeated code.

Yes, unless the programs and service programs are intended to go outside your control, and somebody tries to use a new program, expecting a new call to be available, with an old version of the service program that lacks that call. Just as there's a reason for signatures, and a reason for allowing the developer full control over them, there's also a reason for having *previous and *current signature support.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.