Re: A few questions

[Simon Wright <simon@pushface.org>]

"Randy Brukardt" <randy@rrsoftware.com> writes:

> You'd probably keep some state in the iterator object (some access to
> the file, at a minimum, possibly a buffer). The "cursor" would be the
> character.  Each call to Next would put the following character into
> the "cursor".  Easy-peasy. :-)

It's a pity that Next takes the iterator object as an 'in'
parameter. This means that, in general, the cursor needs to hold the
state. It certainly needs some way of indicating end-of-iteration;
perhaps a sentinel value.

Can I use the same iterator more than once? (so long as the container
hasn't changed, of course - I expect that would count as tampering,
though) If so, that'd explain why Next.Object is an in parameter!