RE: CF-Spec - another call for opinions

[Buck Calabro <mcalabro@xxxxxxxxxxxx>]

>2) Allow EVAL and CALLP to be omitted:

I would elect to have a special delimiter for any ambiguous variable names:
CF "read"=CountBooksRead(MyBookReportList)
CF if read < MINIMUMTOPASS
CF   FailReading(StudentID)
CF else
CF   PassReading(StudentID)
CF endif

SQL uses a similar way to distinguish a column name from a reserved word:
Select "GROUP" from MyTable group by "GROUP"

If you eventually add a new opcode, the program will not compile, but the
simple addition of quotes around the ambiguous variable will clear it up
without having to resort to nasty renaming of variables.  I don't generally
name my variables after reserved words anyway...

Buck Calabro
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---END