Re: read on a do loop

Scott,

Yup,  ReadExample() and MoreRecords() have high cohesion.  It could be a bad
design tradeoff.  Not so bad if they were in a separate module.

The stand alone ReadExample() is doing two things at once.  It's pretty
obvious how it's used in the Do loop but that's 'by context' instead of 'by
contract'.  Wouldn't it be better to code two simpler functions that do one
thing and one thing only and are also self describing?  Is avoiding having
to view those routines to 'see how they work' better than coding a less
complex Do loop?  Does using ReadExample/MoreRecords make it easier to avoid
having to dig into their source to understand those functions?

Paul