|
I prefer using eval. :) Bradley V. Stone > -----Original Message----- > From: Bob Crothers [SMTP:bob@cstoneindy.com] > Sent: Tuesday, October 20, 1998 2:21 AM > To: 'MIDRANGE-L@midrange.com' > Subject: RE: *Blanks and *Blank > > There is a huge difference between what MOVE and MOVEA does. > > MOVE treats the array element like a single field. MOVEA ignores > element boundaries. > > In the example, MOVE will blank out the first element in the array but > > leave 2 thru 100 alone. > > MOVEA will blank out all elements starting with the element > specified...in this case, since you specified 1, the entire array. > > And if you do a MOVE *BLANK ar1 where ar1 is an array and you did not > specify an array element, it will also blank out the entire array. > > The moral is unless you know you need to use MOVEA, you should > probably do a MOVE or MOVEL. > > And of course, there is no difference in the below between *BLANK and > *BLANKS in the below....because there never (that I know of) is a > difference between *BLANK and *BLANKS (besides the S) > > Bob > > -----Original Message----- > From: Patpong W. [SMTP:patpong@zi-th.com] > Sent: Monday, October 19, 1998 9:13 PM > To: MIDRANGE-L@midrange.com > Subject: Re: *Blanks and *Blank > > Hans, > > I think this two keywords may differ when using with array element(s) > such > the following:- > > A is an alpha array with a hundred elements, 1 byte each. > > MOVE *BLANK A,1 > MOVE *BLANKS A,1 > MOVEA *BLANK A,1 > MOVEA *BLANKS A,1 > > So, what is difference for these samples? > > PPW > ---------- > > From: Hans Boldt <boldt@ca.ibm.com> > > To: MIDRANGE-L@midrange.com > > Subject: Re: *Blanks and *Blank > > > > >Maybe this's a stupid question, but please explain it to me. > > >My question is : > > >* What diferences between *BLANKS and *BLANK at RPG ? > > > > No difference. > > > > Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com > > +--- > > | This is the Midrange System Mailing List! > > | To submit a new message, send your mail to > MIDRANGE-L@midrange.com. > > | To subscribe to this list send email to > MIDRANGE-L-SUB@midrange.com. > > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > > | Questions should be directed to the list owner/operator: > david@midrange.com > > +--- > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- > > +--- > | This is the Midrange System Mailing List! > | To submit a new message, send your mail to MIDRANGE-L@midrange.com. > | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. > | To unsubscribe from this list send email to > MIDRANGE-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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.