Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I use a StringReader to turn a string into something I can upload to an SFTP server (it takes a stream). Is there any point in closing that StringReader afterwards? As far as I can see in the source it just sets the string to null…
I could just do it, but since the close method is marked as throwing an IOException and all I have to wrap it in a try catch and the code just ends up looking a lot more horrible than it perhaps needs to be.
If you know you’re dealing with a
StringReaderthat you’ll be throwing away, I don’t see any reason to close it. I can’t imagine any reason you’d be holding a reference to it after you’d close it, so there’s no real benefit to the string being set tonullfor garbage collection. If you were creating a method that takes aReaderthen it might make sense to close it since you don’t know the underlying type.