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




Von meinem iPhone gesendet
Am 05.04.2024 um 17:46 schrieb Brad Stone <bvstone@xxxxxxxxx>:

I always do that too (except I use declared indicators, not *IN ones unless
it's for a display or something)... :)

I also like:
x += 1;

Yes - makes the intention clearer than x = x + 1 IMHO.

Old school RPGers hate that. but I was brought up with Ada, Pascal, C, etc.. :)

BASIC -> Assembly -> Pascal -> C -> COBOL -> RPG ... that's the short form - some turns left and right here and there (COMAL, Perl, Smalltalk, ...).

The poor soul who has to maintain that code will be a "coder".. haha.. they'll understand it except for the *IN50 part unless... if it was

optionIs5 = (option = '5');

They may understand it easier. :)

Well - I honestly don't know - maybe if I would do it like:

ProtectInputFields = (option = '5');

I think that named indicators should tell the intention - but they also hide the connection between RPG and DDS.

So right now, our shop has decided to stay with numbered but standardized indicators.

So *in50 is always DSPATR(PR) for typical edit/view (2/5) forms.

Most probably the "poor souls" after us will get crazy over DDS - but there are good tools for that today, and maybe some AI in 15-20 years will do all the heavy lifting for them (at least that was what we were told about 30 years ago ;-).

D.


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.