×
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.
On 17-Feb-09, at 6:54 PM, midrange-l-request@xxxxxxxxxxxx wrote:
I can't see the advantage of rewriting MOVE and indicator usage in
existing programs. New programs should use the new techniques and
old programs should be changed as needed when they are maintained.
But where's the justification for rewriting the existing programs.
At a practical level a MOVE does the same thing as an assignment ans
SETON does the same thing as a BIF.
It depends what you mean by "rewrite". I would always convert to RPG
IV and then "modernize" the code as I maintained it. And I would use
a tool like Linoma's rather than the standard IBM tool.
If the program is in a constant state of maintenance then I would -
for example - replace *IN87 = *On with *In(SubfileClear_87) + *On
(where SubfileClear_87 is a constant with the value 87). Why _not_
make life easier for others once you have determined what some
arbitrarily numbered indicator actually does?
The critical thing to me is to move the code to RPG IV - then you have
all the great new features available to you when you need them - and
we can avoid questions on the RPG list about "how do I do X in RPG/
400" ... a question that just shouldn't be asked any more.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
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.
midrange.com
