× 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: MIDRANGE-L Digest V3 #28
  • From: "Buck Calabro" <calabro@xxxxxxxxxxxxxx>
  • Date: Mon, 14 Feb 2000 22:45:47 -0500

Jeff wrote:
>> Without %Len, the only other method of determining the length
>> of a strings value without using an array, is to use CHECKR
>> (Check reverse) op code where you check for the first non-blank
>> position of "SomeField" from right to left.
>
>Well, that's what I did, but I so wanted to use a BIF . . .

You still can!  Prototype it and call it something like GetStrLen.  Internal
to the subprocedure use CHECKR.  Or use an array.  Model it both ways and
see which one you like best!  The point is that with subprocedures you can
extend RPG almost as easily as you can extend CL by writing your own
commands... When you switch to RISC you can either leave your home-grown
function, change the internal of GetStrLen to actually use %LEN or
scan/replace and use %LEN instead of GetStrLen.

Buck Calabro
Still enthusiastic about subprocedures after 2 years!  Woo Hoo!


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