× 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.


  1.  Home
  2. RPG400-L
  3. October 2017

Re: *ENTRY PLIST to free-form procedure interface

I feel your pain.  I'm not sure adding a "non-severe" error is the answer, but I'm slightly biased right now because I've been pulling those out recently.  I absolutely loathe compiler errors, but I can't necessarily fault your reasoning.

Whatever your eventual business decision, at least you know your options.  :)

I'm trying to determine a good standard for our "*entry plist" procedure
interfaces, since we're fairly new at using them here. Personally, I think
I'd like to name these procedure interfaces Entry_Plist.
(...)
If I didn't name them
Entry_Plist, I would most certainly need to add a comment at the end of the
DCL-PI statement, i.e.: // <-- *ENTRY PLIST

- Dan


As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.