Re: Closing streams in the destructor

[Matthew Tuck]

Patrick Beard wrote:

> As far as knowing whether a file has been closed, it should be safe to
> call Close() multiple times, that is to say, the method should be
> "idempotent."

Yes, but as I said, IMO it would be nice to be able to detect "leaky"
classes that don't call close, and idempotent close does nothing to help
that.

-- 
         Matthew Tuck: Software Developer & All-Round Nice Guy
     My experience is that in general, if there's jobs programming
                 in it, it's not worth programming in.