Julian Fitzell wrote:
> Hmm... well that's certainly another option, but I don't think that 
> excuses us from having a file size primitive that returns an incorrect 
> answer... does it?  (wondering only because maybe there's some reason 
> why you'd rather have the file size when you opened the file?  can't 
> really think of one...)

Avi points out that I should mention that this was causing file 
corruption as a stream was calling #setToEnd then writing, unfortunately 
in the wrong place since the size of the file was returned incorrectly.

Julian