Re: Alternatives to MOVEL - just curious

One thing with the new full free-format support - one can mix fixed and free in the same code stream. And that without any of the /free - /end-free markers.

So for me, at least, some of the ugliness has gone and actually allows, if needed, the use of these fixed-format opcodes. I always liked more what SCAN did than what %scan did - the filling of an array of positions for found instances of the search was really handy.

Of course, for replacing all those instances, the new %scanrpl - cool - but I can envision situations that do not require replace, but do require processing of each found instance. - The array output then is really good for the work at hand.

Vern

On 12/9/2013 4:42 PM, CRPence wrote:

On 09-Dec-2013 10:29 -0800, Vernon Hamberg wrote:

On 09-Dec-2013 08:31 -0800, Vernon Hamberg wrote:

I'm looking at some code - the purpose is to put the 1st 4 digits
of a 6-digit variable into a 4-digit numeric variable.

It is being done with the MOVEL opcode now.

I'm wondering about efficient alternative methods. One I can think
of is to use a data structure -

dcl-ds dsMoveL qualified;
num4 zoned(4);
num6 zoned(6) pos(1);
end-ds;

Anything simpler? Better performing?

I hope the syntax is right!! But you get the idea, right?

<<SNIP>> we're dealing here with things that will never involve
calculations - IDs stored as zoned data types. MOVEL has the
advantage that it's not really a calculation in the sense of an
expression, it's a kind of memory operation, seems to me. <<SNIP>>

-snip-

Moving the /fixed-format/ code elsewhere, a
subprocedure, to avoid its ugliness remaining inline to the
since-modified to free-format code, might best just code the original
MOVEL and be done with it.? It all depends of course, on what the code
really *needs* to do to make everything work, while avoiding any
unnecessary breakage; however /broken/ might be defined :-)
http://archive.midrange.com/rpg400-l/201308/msg00134.html