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



Blake, thank you for your description of what RDP does. It totally
sounds like it would be helpful, but getting my employer to spend hard
dollars is always a struggle.

Bryce, I will have to do more research. Large portions of our
codebase are still RPG III, and if I understand correctly, there isn't
a way to incorporate any ILE benefits to those until they are at least
converted to RPG IV. We do write almost all of our new RPG in RPG IV
(making use of the better syntax and BIFs and so forth but minimal if
any use of ILE), but right now I think there are still too many
critical RPG III pieces that we find it very daunting to make the
wholesale switch. (I fear some of those old pieces make use of
dubious older features and methodologies that I don't think we can
just use the automated converter to convert them all without breaking
something.)

I fully understand that most of the problem is irrational on our part,
but we do our best to knock the pieces we do touch into better shape
than they were before.

Dennis, I realize most assemblers for a very long time have not
required things to be in *specific* columns. However, my point is
that long-time users of legacy RPG get used to seeing things formatted
in that *style*. If you take a piece of columnar RPG code out of SEU
and paste it into a plain editor, then adjust all the opcodes to be
further to the right by a space or two, that does not change the human
readability practically at all, especially in RPG IV. SEU may care,
and the compiler may care, but the human typically doesn't.

Also, I think some older programmers (subconsciously) are aided by the
fact that only so much can happen on one line of traditional RPG.
When you can have arbitrary expressions (and this applies to EVAL, IF,
DOW, etc. just as much as /free), you can start to pack a lot more
into a line (and sometimes more and sometimes less), and for some
brains, it makes each line harder to parse.

When it comes to /free, I also have the peculiarity that I'm now used
to not having semicolons at the end of my lines. I find it especially
jarring that even an if statement needs a semicolon after it, because
this isn't how C works. (This is more of a writing hiccup than a
reading one.)

John

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.