Re: CF-Spec - another call for opinions

> So, please consider and choose one of the following options:
> 
> 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
> 
> 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
> 
> 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.
> 
> 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?
> 
> 5) Is there some other alternative we've missed?
> 
> 
> As usual with this kind of poll, comments on the issue are
> welcome.
> 
> Cheers!  Hans
> 
> Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.com

2 is best, 1 is ok, 4 is least desirable

Joe Teff

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