• Subject: Re: Parameters
  • From: "William Corbett" <corbett@xxxxxxxxxxxxxxx>
  • Date: Sat, 27 Jan 2001 01:20:28 -0500
  • Importance: Normal

This is a hashed and rehashed problem here  I fought with this for a while,
then wondered - Why?
Yea, yea, yea.  CL wants numerics to be 15 5, but who cares?  I seldom want
my numerics to be 15  5.
As for myself, I quit fighting with it about years ago.  I never have this
problem...I haven't passed a "numeric" to an RPG in years.

This is kinda like "Hey doc, it hurts when I do this".  "Well don't do that

Don't pass a list of parameters back and forth between CL and RPG.  Pass a
data structure instead.  This ALWAYS works.
My calls always look (something) like this:

C                     Call         "PROGRAMA"
C                     Parm                          aparm

Where aparm is the RPG data structure, containing whatever you want.
You're always passing "character" data, never any problems.

If the OS gets smart-alecky and tries to "optimize" by chopping off blanks
(it thinks is "white space"), just make the RPG DS one byte longer than the
CL definition, add a 1-byte filler field with a char (I use "X") in it.  I
do this when some char fields, which could be blanks, fall at the end of the
data structure.

Stringing and unstringing in the CL is a small price to pay, in my opinion.


| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

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