The best way would be to create a program that goes through the compiler
listing, generates the field types and lengths for each field, and then
checks the MOVEs.  MOVE from one field to another of the same type and
length could be switched, and other MOVEs could be flagged.

The hard part would be fixing the non-standard moves.  But I'd be
interested to see the percentage of "standard" vs. "non-standard" moves.

Joe

> From: rob@xxxxxxxxx
> 
> 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?



As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2025 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.