RE: CF-Spec - another call for opinions

["John Taylor" <john.taylor@xxxxxxxxxxxxxxx>]

> 2) Allow EVAL and CALLP to be omitted:
>
>       CF KeepLooping = *ON
>       CF dow KeepLooping
>       CF    read MasterFile
>       CF    if %eof
>       CF       HandleEndOfFile()
>       CF    endif
>       CF enddo

This would be my first choice.

> 3) Option 2 with a commitment from us that no new opcodes will
>    conflict with any possible variable or procedure name.  For
>    example, opcode ON-ERROR could never be confused with a var or
>    proc name.  This may mean some goofy looking opcodes in the
>    future.  On the other hand, since most enhancements these days
>    seem to be in BIF's, this may not be too big a deal.

Don't even need that commitment. I have no problem with the compiler issuing
an error if it finds a variable declaration or procedure name that conflicts
with any current, or future "reserved" name. Even for existing applications,
it is not that big a deal to change a procedure name if you need to.


> 1) Make EVAL and CALLP always required:
>
>       CF eval KeepLooping = *ON
>       CF dow KeepLooping
>       CF    read MasterFile
>       CF    if %eof
>       CF       callp HandleEndOfFile()
>       CF    endif
>       CF enddo
>

This would be my second choice - if you REALLY have to do it that way.

>
> 4) Optional EVAL and CALLP, but use some special character to
>    distinguish opcode names from var or proc names:
>
>       CF KeepLooping = *ON
>       CF /dow KeepLooping
>       CF    /read MasterFile
>       CF    /if %eof
>       CF       HandleEndOfFile()
>       CF    /endif
>       CF /enddo
>
>    If you don't like "/", what about some other character?

Yuck! This is the absolute worst. My fingers are getting sore just thinking
about all the additional typing.

> 5) Is there some other alternative we've missed?

Not another alternative.. just another request... any way to drop the "CF"
as well?


BTW, thanks for allowing us to have some input into the decisions.


John Taylor

+---
| 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