Re: *ENTRY PLIST to free-form procedure interface -- 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: *ENTRY PLIST to free-form procedure interface
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Tue, 10 Oct 2017 17:44:36 -0400
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 10/10/2017 5:26 PM, Dan wrote:

I'm trying to determine a good standard for our "*entry plist" procedure
interfaces, since we're fairly new at using them here.

I shamelessly stole Rob B's idea of commenting them like so:

// *ENTRY PLIST
dcl-pi *n...
...
end-pi;

This works great for my old muscle memory which insists on searching for
*ENTRY... :-)

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: *ENTRY PLIST to free-form procedure interface , 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.