× 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: Numeric parameters between RPG programs
  • From: Mark Lazarus <mlazarus@xxxxxxxx>
  • Date: Mon, 01 Jun 1998 22:27:04
  • In-Reply-To: <199805280410.XAA22833@iria.inwave.com>

Pete,

At 10:45 PM 5/27/98 -0500, you wrote:

>I fought this on V3R1, but I thought this behavior had been changed. When
you defined a numeric variable with Like(), it was always assigned the
default (packed) storage type. You can confirm this in your program by
searching the field definitions at the end of the compiler listing for the
variable name. At least at V3R1, you couldn't specify the storage type on a
D spec that used Like(). It was a little maddening. I was forced to hard
code some field lengths so that I could specify the storage type <grrrr>.
So much for data independence. This was not considered a bug. I guess that
makes it a feature. I haven't tried it lately. Don't write much RPG any more.

 If I'm not mistaken, LKE() in the D spec works as it's supposed to.  It's
the C spec LIKE() that is skewed.

 -mark

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