Re: CF - One last question

["Eric N. Wilson" <doulos1@xxxxxxxx>]

I was under the impression that for file IO the CF specs would be sort of
like the following
CF  CHAIN(READ : READ) // File name Read, Data Structure READ
CF  WRITE(READ : CHAIN) // File name READ, Data Structure CHAIN

CF  UPDATE(CHAIN : READ) // File name Chain Data Structure READ
CF  READ(WHEN : CHAIN) // File Name WHEN Data Structure CHAIN
CF  READE(WHEN : UPDATE : READ) // File Name WHEN, Search Argument UPDATE,
Data Structure READ

Note: I think I would have to shoot the programmer who would write code like
this.

Also concerning the CALLP thing in most other languages you can not assign a
value to a function.

That is
CF Fred = Flintstone

Should be ok even if an opcode or function was created with the name fred as
you can not have a function as the left hand side of an expression and the
compiler would know that rule so it would look up the name Fred in the
variable pool rather than the function pool. I would think that adding the
parens on the end of function calls that do not have a return val ( and even
perhaps those that do have return vals) should be sufficent to identify them
as function calls rather than variables. As long as IBM continues their
naming convention of prepending a '%' to the name of a BIF and we do not use
the '%' as a first character we should continue to be ok.

Just my thoughts
Eric
______________________________________________
Eric N. Wilson
President
Doulos Software & Computer Services
2913 N Alder St
Tacoma WA 98407


----- Original Message -----
From: John P Carr <jpcarr@tredegar.com>
To: RPG400-L <RPG400-L@midrange.com>
Sent: Sunday, August 15, 1999 11:42 AM
Subject: Re: CF - One last question


> >Hans & Barb
> >Would these still be valid in the CF specs ?
> > CF   READ  CHAIN READ
> >CF   WRITE READ CHAIN
> >CF  UPDATE CHAIN READ
> >CF  READ WHEN CHAIN
> > and maybe in the next release,
> >CF  UPDATE READE WHEN READ
>
> Gee, Didn't anyone take this seriously ??  I know Hans won't see it till
> monday,
> but I thought at least someone would be curious about how the parser would
> interpert these.  Maybe you thought I was kidding.
>
> These are all valid statements in RPGIV,   How in a free format
environment
> without Keywords, and/or special characters will the parser perceive
these?
> (BTW, IBM did the special character idea for their stuff using the % for
> BIF's,
>  They could have been consistent perhaps sticking with the *)
>
> Note;  the
>
> CF UPDATE CHAIN READ
>
> Actually has two valid meanings in RPGIV(depending on which position
> you put stuff)
>
> I guess we may findout what the parser thinks of our file names, field
> names,
> and variable names when we go to compile the stuff eh?
>
> As an anecidote,  I remember sitting with the developer of the source
level
> debugger while it was still in design mode.    He was talking about how
good
>
> the parser was,    I said,   "Key in   WHEN WHEN.....  "
>
> He did and the debugger "Thru up" so to speak.  I said that's what will
> happen
> if I have a variable  named WHEN.  Everyone in the room thought it was
very
> funny.
>
> I been thru this phase before,  and I want to be sure that things work
like
> we
> think they will.  Remember we're affecting about a Million programmers
here,
> who all have their own ideas about file, field, and variable names.
>
> For example, on the CF UPDATE CHAIN READ statement
> Just what should the compiler take for granted?  How will it really
> know what I meant?   And, No I don't think quotes 'UPDATE'  (like SQL)
will
> work.   You tell me why.
>
> This is the fun part.
>
>
> John Carr
>
>
>
>
> +---
> | 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
> +---

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