Re: Chain doesn't set %EOF

["Paul Morgan" <pmorgan@xxxxxxxxxxxxxx>]

A new %DATA BIF would work but why add a new BIF that isn't really needed?

The same %EOF vs %FOUND argument could be made about a ReadE.  When I do a
ReadE and it sets on %EOF it's not really at End Of File but at the end of
the read group.  As far as I'm concerned a Chain opcode is really just a
shortcut opcode for a SetLL/ReadE combo.  It should function the same way.
I'd also mention the %EQUAL BIF set by the SELL opcode isn't set by the
CHAIN opcode.

Paul

-- 
Paul Morgan
Senior Programmer Analyst - Retail
J. Jill Group
100 Birch Pond Drive, PO Box 2009
Tilton, NH 03276-2009
Phone: (603) 266-2117
Fax:   (603) 266-2333

"Joe Pluta" wrote

> Hi Paul!
>
> The thinking is that you didn't actually hit end of file.  Only a READ
> can hit the end of file; CHAIN can only either find or not find a
> record.  Yeah, it's a pain in the butt because it blows up the shortcut
> that many of us have used for 20 years or so.
>
> I understand the thinking that %EOF and %FOUND are different.  How about
> a new BIF that does what we want?  Like %DATA.  If a CHAIN *or* a READ
> are successful in putting data into the buffer, then %DATA is true.  We
> could then do this:
>
> Chain ( SomeKey ) File;
> DoW %Data( File );
>    // do something
>    ReadE ( SomeKey ) File;
> EndDo;
>
> Joe