|
jt, <snip> > I'm talking that a BIF should be IN A KNOWN STATE. It's either on or off, > and that SIGNIFIES the known state. So it would be a case of either the > CHAIN should do nothing whatsoever with the %EOF, which makes a lotta sense > to me. Or it should set it one way or the other. <end snip> The KNOWN STATE that the %EOF BIF reflects is the status of the file pointer - it is or isn't at EOF. A READ etc. moves the pointer, therefore it can change the state of EOF. A CHAIN can only move the pointer IF the record was found. Only a successful CHAIN can change the state of EOF. If the %EOF BIF is to reflect the KNOWN STATE then this is the way it must work. Paul
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.