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

Re: PR & PI field definitions

On 6/24/2013 7:48 PM, Booth Martin wrote:
In this code:

FSTATES if e k disk

// ...................... Prototype
D GETSTR pr
D 2
D 20
// ....................... Procedure interface
D GETSTR pi
D pSt like(ST)
D pState like(STATE)

What am I missing? Do I have to hardwire the field sizes of the fields
in the PR?

I would. The PR/PI is a contract between the caller and the callee,
enforced (more or less) by the compiler. I don't want this contract to
ever be accidentally broken by someone compiling a file. If that needs
to happen and I need a new contract, I write a new function.

It'll be interesting to hear other opinions.
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...
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.