× 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: what is unclear about 01 02 03 -Reply
  • From: Hans Boldt <boldt@xxxxxxxxxx>
  • Date: Tue, 5 May 1998 08:20:48 -0400

Walden wrote:
>Sorry to say, but l-hand indicators can be _easier_ to understand than
>"structured" code. Compare
>
> key chain rcd  90
>90  leave
>
>with
>
> key chain rcd  90
> *in90 move  rcdnf
> rcdnf ifeq *on
>  leave
>  endif
>
>You tell me which is easier to read.

I can't believe this discussion has gone on so long.
(And I can't believe I'm responding!)

Add this snippet of V4R2 code and tell me what's more
readable:

     C                  CHAIN     rcd
     C                  IF        NOT %FOUND
     C                  LEAVE
     C                  ENDIF

Fact is, the traditional indicators are becoming a
thing of the past.  As of V4R2, there are very few
cases where an old-style indicator is still needed.
Eventually, we'd like to make it even easier to
avoid them entirely, using techniques that do not
require compromising readability.

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@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-Ups:

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.