|
Date: Wed, 6 Jun 2001 13:46:59 -0400 From: jpcarr@tredegar.com Subject: Re: MOVEA -> EVAL >>But, I'm still waiting for someone to post an example where using MOVEA is >>the best solution :) >>Barbara Morris > > MOVEA arr1(n) arr2(m) Aw, c'mon, John. I mean where the whole solution to a programming problem requires the use of MOVEA at all. What are you going to do _after_ the MOVEA? Are you going to write a loop to mess with the array and then use another MOVEA to copy it back? I want an example where MOVEA is required, not where MOVEA is the best way to do the function of MOVEA. (I agree that if (big if) there really is a reason to use MOVEA, then MOVEA is probably the best thing.) >Simple easy to read code, that hides the complexities of the task at hand >so that the meaning of the "application code" will not be obscured by >coding gymnastics. My awful pointer example was not the true suggested replacement for MOVEA. The true suggested replacement for MOVEA is to replace ALL the code surrounding the MOVEA with a simple string operation. No coding gymnastics (which imo includes the use of MOVEA), no pointers or overlays needed, simple and understandable. Barbara +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.