Re: OMG MOVE sucks!

On Thu, 19 Sep 2019 at 15:00, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

On Thu, Sep 19, 2019 at 2:16 PM Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 9/19/2019 12:50 PM, John Yeung wrote:

If you find yourself dealing with a program which is chock full of
MOVE*

-snip-

I think I had an easier time than most because of my background as an
assembly language hobbyist, but when working in one of these old
programs, I think of MOVE* as an overloaded operator and that keeps me
on the straight and narrow.

An easier time with what?

It sounds to me as though you're saying your assembly background helps
you use MOVE* "correctly".

Yes. Learning to use, read, and debug the use of MOVE* was easier for
me than for most because I came from assembly.

My contention is that we're well past the time when there is such a
thing as using MOVE* correctly, other than *not* using it.

Sounds good to me.
Aside from very carefully commented code wrapped in a sub-procedure, I
haven't used MOVE and friends in more than a decade. And then, only
very rarely.

The point of my reply was to try to explain how I deal with old code
that has MOVE as an intricate part of its function.
--buck
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com