RE: Mass conversion of MOVE to EVAL.

Rob,
        Have you thought about trying Linoma's RPG tool box? We have it and
I tried the convert tool and told it to translate MOVES and MOVELS with data
to EVAL statements and it did it with some difference from what some might
expect. For example MOVE 'NNNN' MYFLD1 5 got converted into EVAL
%subst(MYFLD1:2:4) = 'NNNN' (MYFLD1 was defined in the D-Specs which is
required for the above example).   

        The price is good for iSeries software and it will also convert
RPGIV code converted by IBM's basic conversion tool into better RPGIV code
plus you can also convert RPGIV to /FREE format for those statements that
fit into /FREE.
http://www.linomasoftware.com/products/rpgtoolbox/index.html


Thank you,
Matt Tyler
WinCo Foods, LLC
mattt@xxxxxxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, August 09, 2005 2:56 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Mass conversion of MOVE to EVAL.

If you suspect that the only use of MOVE was the fact the gent started 
coding before EVAL existed,
and,
there were no 'tricks' done with MOVE,
what do you think about doing a mass search&replace on MOVE with EVAL?  If 
I immediately recompile and it goes successfully what problems would a 
hidden trick play that the compiler wouldn't catch?  For example, moving 
alpha to numeric, or vice versa, would blow the compile, right?  Then I 
would know that I need to handle that on a individual basis.

MOVE CHAR15  CHAR4
sure behaves differently than
EVAL CHAR4=CHAR15
Would this be flagged on a compile listing as a low level warning?  And 
vice versa flagged also?
(Just tried it.)
Answer is no.

Any compiler option that will have it generate a message?

Goal:  Convert all these silly MOVEs to EVALs as a first step to 
converting the source to free format.

Rob Berendt