Re: CF - One last question

[boldt@xxxxxxxxxx]

John wrote:
>No, Actually I was referring to the idea that we may be able to
>read/chain/etc an
>externally defined file into a data structure (named Read in my example).

OK, I picked that up from subsequent discussion.  Maybe
I wasn't awake yet when I replied to your original note.
Or maybe it just hadn't occurred to me that you might
have misunderstood the CF-Spec design.

>
>And No,  you know my code doesn't look anything like this,  However
>you also know I tend to ask the questions for other people rather than
>myself.
>
>BTW,  on the
>CF    UPDATE CHAIN    READ
>
>How do you know which I'm doing ?  CHAINing to file READ using keylist
>UPDATE,
>or UPDATING file CHAIN  thru data structure  READ  ??

It is quite clear.  You are doing an UPDATE operation.
On a CF-Spec, as with other languages, the first thing
on the statement is the opcode.  (With the exception, of
course, that EVAL and CALLP may be optional.)

Did you really think we hadn't thought through the
design well enough?  I'm not sure whether or not we
should feel insulted by your implication!

>
>Another BTW,  Questions like "Would you code like that"  have as much
>value in this stage of design as "Why would one ever use DOW when we
>have a pefectly good DOU"

The question, was of course, rhetorical.

I agree.  And our own early experience in coding the
CF-Spec in our own RPG code is helping us tweak the
design, as you've no doubt noticed.

>
>How about that IFS support??

How about that IFS support?  You'll have your chance to
vote for it in the next enhancement poll.

BTW, have you never thought of coding a SPECIAL file
interface to handle IFS files?

Cheers!  Hans

Hans Boldt, ILE RPG Development, IBM Toronto Lab, boldt@ca.ibm.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
+---