On Dec 08, 2006, at 12:18 PM, Charles Yeomans wrote:
On Dec 8, 2006, at 2:09 PM, Norman Palardy wrote:
On Dec 08, 2006, at 11:58 AM, Charles Yeomans wrote:
I wouldn't expect it to because of the nature of the string
concatenation in this code. Below is a version that replaces the
string concatenation with something faster. I also changed the
while loop to a do loop and replaced the evil Close methods.
EVIL close methods ?
Is there something about closing an input out output text stream
that is "evil" ?
There is no way to reopen a stream. There is no way to check
whether a stream has been closed. Setting the object reference to
nil when you're finished with it means that you don't need to check
whether it's been closed. And should you ever refactor your code
so as to pass a reference to that stream to another method, your
code has a better chance of working.
I see
Sounds like a shortcoming in the input and output streams that you
cannot tell these things or reopen them perhaps
Here I thought there was a bug related to closing a stream that might
cause problems
It's a practical deficiency in using them
I've run into this as well but dealt with it differently
Just for everyone else the relevant bug reports are
http://www.realsoftware.com/feedback/viewreport.php?
reportid=zvwedvoj
http://www.realsoftware.com/feedback/viewreport.php?
reportid=kluojbyk
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
