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



I would agree Buck, but as I am sure you know; sometimes we do not get to
decide on the coding standards and processes. We are making improvements
and I am working on adding additional skills that I just did not need before
or never thought of using.



-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Buck
Sent: Friday, July 20, 2007 12:15 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Sub-Procedures (Follow-up Question)

Jon Paris wrote:
There is only one "nuance" in program parameter passing normally and that
is
to realize that if a program is called from the command line that numeric
parms are 15,5 packed - I won't go into the rest of it here - it is well
covered in the FAQ. Quite why some shops adopt the char method of passing
parms and the resulting error prone code that goes with it is a mystery to
me.

Jon, I know that _you_ understand this, but since this is one of my hot
buttons I'll kick in my opinion for the greater good. Passing by
character doesn't help either because long character fields have the
exact same problem when passed as literals. Long is greater than 32
characters. It's in the FAQ. Search for 'garbage' http://faq.midrange.com

Jon is absolutely right that you really ought to pass the actual data
type rather than force everything to character and back. Let the
compiler help you with your coding chores...
--buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.