Re: Why does this compile?

Interesting point.  What is the operator precedence?  + or =?  A quick google found https://en.cppreference.com/w/c/language/operator_precedence, which says + comes before =, although that's for C and it's more mathematically speaking than string manipulation.

Anyway, assuming that's the case, all this:

'*** ' + %trim(sdprogram) = ': Price Change Report ' + 'has completed for Customer #' + %trim(%editc(e1cust : 'X')) + '.'

would be

'*** ' + %trim(sdprogram)

 =

 ': Price Change Report ' + 'has completed for Customer #' + %trim(%editc(e1cust : 'X')) + '.'

Since those are obviously never going to be the same, the result would be false, or '0'.


Then the question is, what does wrt_job_log('0') do?

Was there a joblog entry with just '0' in it?

--
*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
petercdow@xxxxxxxxx <mailto:petercdow@xxxxxxxxx>
pdow@xxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxx> /

On 7/16/2021 11:02 AM, Justin Taylor wrote:

I'd guess it treats this as a boolean.
"%trim(sdprogram) = ': Price Change Report '"


date: Fri, 16 Jul 2021 10:24:36 -0500

from: DEnglander--- via RPG400-L <rpg400-l@xxxxxxxxxxxxxxxxxx>
subject: Why does this compile?

I have a piece of code that compiles with no errors. It runs, but doesn't
do anything.

Here is the code:


wrt_job_log('*** ' + %trim(sdprogram) = ': Price Change Report ' +
'has completed for Customer #' +
%trim(%editc(e1cust : 'X')) + '.');


I accidentally typed an equal sign and it should be a plus sign right
before the colon. The compiler took it, compiled it with no error, but
when the program gets to the line, it doesn't write a job log entry.

Once I saw the problem, I changed the = to a plus, recompiled and reran.
There is now an entry in the joblog.

Prototype wrt_job_log accepts a CHAR(512) field with CONST defined.

Is this a compiler bug?


Doug