On 2007-01-23, at 01:05, Charles Yeomans wrote:
As I've said before, the better practice is not to use Close.
Instead, set the stream object reference to nil when you're done.
Charles Yeomans
On Jan 22, 2007, at 6:51 PM, Sven E Olsson wrote:
Here is an interesting report about the TextOutputStream.Close method
I have found some "issues" in my app like I think files is not
closed properly ...
Could it be some problems with the close method? .. don't know but
here is a report i found...
Please vote, I think this must be the most used functions and it
not work properly...
http://www.realsoftware.com/feedback/viewreport.php?
reportid=kluojbyk&cmd
Thanks for the response (Joe/Charles)
I think I should give this a try....
But as in your report and example, close the file and then write
again to it - then it looks like the file is NOT closed. So if I in
an another method try to Save the file I get error .... (104) and I
have to close the app and restart to be able to Save the file again.
This happens, but not often...
Sven E
-----------------------
REALbasic 2007R1 OS X 10.4.8 Intel and 10.4.6 PPC
SEEdit Maxi THE XHTML EDITOR FOR MACINTOSH
http://www.seedit.info
_______________________________________________
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>
