Re: Let versus Move

["Morgan, Michael" <MiMorgan@SBHCS.COM>]

un-subscribe

> -----Original Message-----
> From: Johnson, Dan [SMTP:Dan_Johnson@WRIGHTEXPRESS.COM]
> Sent: Friday, August 27, 1999 3:39 PM
> To:   Multiple recipients of list SQR-USERS
> Subject:      Re: Let versus Move
>
> If you take the SQR training courses offered by Scribe they recommend that
> you use the move command for simple assignments like move 0 to #count or
> move 'yes' to $ans and use let for complex assignments like
>  let #x = 5 * 5 / 3 or let $ans = 'yes' || 'maybe'. The reason is that let
> has more processor overhead. I am not sure why this is the case but my
> theory is that move does a simple register copy whereas let is probably
> running through multiplexers or some other complicated machine stuff
> (systems is not my forte). This also holds true for the add, subtract,
> multiply, and divide commands, that is they have less overhead than let.
> The
> code that I have inherited has mixed use of all of these commands with no
> rhyme or reason.
>
> Dan.
>
>         -----Original Message-----
>         From:   Love, Kristin [SMTP:klove@MSA.COM]
>         Sent:   Friday, August 27, 1999 12:48 PM
>         To:     Multiple recipients of list SQR-USERS
>         Subject:        Re: Let versus Move
>
>         But I heard somewhere that the LET command uses more processing
> time
> than
>         the MOVE command. Don't ask me why, I just believe what I'm
> told...
>         :) Kristin
>
>         > -----Original Message-----
>         > From: Jay Chin [SMTP:jaychin@US.IBM.COM]
>         > Sent: Friday, August 27, 1999 12:33 PM
>         > To:   Multiple recipients of list SQR-USERS
>         > Subject:      Re: Let versus Move
>         >
>         > Joe,
>         >
>         > There isn't any reason to do let and move to the same variable.
> There's
>         > just
>         > many ways to do the same thing in SQR.  For instance, let #x =
> #x
> + 1 is
>         > the
>         > same as add 1 to #x.
>         >
>         > Regards,
>         >          Jay Chin
>         >
>         > PeopleSoft Integration Services / IBM Global Services
>         > Voice  (301) 803-2799
>         > Fax      (703) 237-9635
>         >
>         >
>         > Joe <jejohn1216@SURFREE.COM> on 08/27/99 11:12:21 AM
>         >
>         > Please respond to SQR-USERS@list.iex.net
>         >
>         > To:   Multiple recipients of list SQR-USERS
> <SQR-USERS@list.iex.net>
>         > cc:
>         > Subject:  Let versus Move
>         >
>         >
>         >
>         >
>         >
>         > Greetings, SQRUG
>         >
>         > I inherited an SQR that has the following code in a procedure
> called
>         > get-timelines:
>         >
>         >  let $firstline = 'Y'
>         >  let $tl_cust_id = ' '
>         > .......
>         >  let #pbill_tot_fee_expense = 0
>         >  let #pbill_tot_oth_plcmnt_exp  = 0
>         > .......
>         >  move 0 to #pbill_tot_oth_plcmnt_exp
>         >  move 0 to #pbill_tot_fee_expense
>         > .......
>         > begin-select
>         > .......
>         >
>         > I know the procedure is to set values to 0, but I don't see why
> you need
>         > to do
>         > Let and Move to the same variable.
>         >
>         > SQR Server Manual says that:
>         > LET assigns the value of an expression ('0') to a
> string/numeric/date
>         > variable,
>         > and that
>         > MOVE moves one field ('0'?)to another field and provides the
> option of
>         > edits to
>         > the field.
>         >
>         > Can someone explain this to me?
>         >
>         > As Always, TIA
>         >
>         > Joe Johnson
>         >
>         >
>         > ~~ JEJ ~~   ;{)
>         >
>         > __________________________________________
>         > $14.95 a month Unlimited Internet Access.
>         > Get your first month for $1.00.
>         > http://www.surfree.com/promo