Re[2]: Using *blank in a CL program

["Todd Sabella" <Todd.Sabella@xxxxxxxxxx>]

     The CL compiler treats *blanks as a character constant.  Since the constant
     *blanks doesn't contain blanks or single quotes, it isn't required to be
     surrounded by single quotes.  Therefore, SEU and the compiler didn't see a
     problem.

     If (&testfld = *blank) really means
     If (&testfld = '*blank')

     Most programmers, including me, put all character constants within single
     quotes, even though they aren't always required.

     Todd


______________________________ Reply Separator _________________________________
Subject: RE: Using *blank in a CL program
Author:  rpg400-l@midrange.com at INTERNET
Date:    9/12/2001 1:59 PM


> -----Original Message-----
> From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]
On
> Behalf Of Jim_Hawkins@tsss.com
> Sent: Wednesday, September 12, 2001 1:40 PM
> To: rpg400-l@midrange.com
> Subject: Using *blank in a CL program
>
>
> We have a young programmer.  He was writing a CL program and wanted to
test
> and determine if a field was blanks.  He wrote  If (&testfld = *blank)
....
> We found that program compiled this way but did not accurately test
for a
> blank field.  We changed the program to test for '  ' and the program
> worked.
> We found no reference to *blank in the CL manuals and are surprised
that
> program compiled with this value entered.  Does anyone have a thought
on
> this?
>
> Jim Hawkins
> Pgmr/Analyst
> Triple S Plastics, Inc.
     >