RE: Eval *= -- RPG400-L

Subject: RE: Eval *=
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Wed, 11 Apr 2018 17:08:21 +0000
List-archive: <https://archive.midrange.com/rpg400-l/>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Equivalent to:
@CurrOptFntSiz = @CurrOptFntSiz * (1+(@PzFactor*.01))

-----Original Message-----
From: Versfelt, Charles [mailto:CVERSFELT@xxxxxxxxx]
Sent: Wednesday, April 11, 2018 9:25 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Eval *=

Checking a program that bombed, I came across this line of code.
C eval @CurrOptFntSiz *= (1+(@PzFactor*.01))

I don't think I recall seeing *= in an eval statement.
The compiler certainly accepted it.
Is this multiplying @CurrOptFntSize by (1+(@PzFactor*.01)) and setting @CurrOptFntSize equal to that?

Charlie

This email message has been scanned for viruses and malware by Mimecast.

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.