RE: MOVE opcode in freeform (was Strange behavior w/%editc)

["Bob Cozzi \(RPGIV\)" <cozzi@xxxxxxxxx>]

Mark,

You're right, and you've actually subtlety stated the following:

If the need for the function of MOVE/MOVEL exists, then why not make it
as easy as possible to do? Why make use (the RPG programmer) jump
through hoops just to accomplish something as elegant as MOVEL?

Case in point, the story behind the EVALR operation code.

Bob Cozzi
cozzi@rpgiv.com
Visit the on-line  Midrange  Developer  forum at: http://www.rpgiv.com


> -----Original Message-----
> From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]
On
> Behalf Of M. Lazarus
> Sent: Wednesday, February 27, 2002 6:56 PM
> To: rpg400-l@midrange.com
> Subject: RE: MOVE opcode in freeform (was Strange behavior w/%editc)
>
> Hans,
>
> At 2/27/02 01:50 PM, you wrote:
> >Yes, to properly convert MOVE/MOVEL to EVAL, you need to
> >do some funny gymnastics to duplicate the exact semantics
> >of the MOVE.  But which operation is more common:  Full
> >replacement of the value in the target variable?  Or just
> >changing right-most (or left-most) bytes?
>
>   MOVE, MOVEL and EVAL are functionally different and there's no good
> reason that that functionality cannot be preserved.  Since we are
primarily
> using EVAL (or an assignment operator), using MOVE/MOVEL will
highlight
> that this is a special case.  Therefore I think that it would be very
> useful to preserve these opcodes, instead of having to jump through
BIF hoops!
>
>   -mark
>
> _______________________________________________
> This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing
list
> To post a message email: RPG400-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
> or email: RPG400-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/rpg400-l.