FxCop might help (although it didn’t spot a test I just fired at it); but yes: you are meant to check. IDisposable is simply such an important part of the system that you need to get into this habit. Using intellisense to look for .D is a good start (though not perfect). However, it doesn’t … Read more
No, it’s not. using ensures that Dispose() will be called, which in turn calls the Close() method. You can assume that all kinds of Streams are getting closed by the using statement. From MSDN: When you use an object that accesses unmanaged resources, such as a StreamWriter, a good practice is to create the instance … Read more
Beginning with C# 8.0, the using keyword can be used as an attribute in the variable declarations of disposable objects (Reference). The semantics is as you would expect — the objects are auto-disposed at the end of the scope. public class Disposable : IDisposable { string name; public Disposable(string name) { this.name = name; } … Read more
EDIT: There seems to be some inefficiencies with closing and reopening the client multiple times. I’m exploring solutions here and will update & expand this code if one is found. (or if David Khaykin posts an answer I’ll mark it as accepted) After tinkering around with this for a few years, the code below is … Read more
One option, which is somewhat nasty but would work, based on the fact that the C# compiler calls Dispose only if the resource is non-null: protected void ValidateExportDirectoryExists() { using (useNetworkAccess ? new Core.NetworkAccess(username, password, domain) : null) { CheckExportDirectoryExists(); } } Another alternative would be to write a static method which returned either null … Read more
When you see a using statement, think of this code: StreadReader rdr = null; try { rdr = File.OpenText(“file.txt”); //do stuff } finally { if (rdr != null) rdr.Dispose(); } So the real answer is that it doesn’t do anything with the exception thrown in the body of the using block. It doesn’t handle it … Read more
A using statement should be used every time you create an instance of a class that implements IDisposable within the scope of a block. It ensures that the Dispose() method will be called on that instance, whether or not an exception is thrown. In particular, your code only catches managed exceptions, then destroys the stack … Read more
Yes, you can also put them in one using statement: using (MemoryStream data1 = new MemoryStream(), data2 = new MemoryStream()) { // do stuff }
Java 7 introduced Automatic Resource Block Management which brings this feature to the Java platform. Prior versions of Java didn’t have anything resembling using. As an example, you can use any variable implementing java.lang.AutoCloseable in the following way: try(ClassImplementingAutoCloseable obj = new ClassImplementingAutoCloseable()) { … } Java’s java.io.Closeable interface, implemented by streams, automagically extends AutoCloseable, … Read more
That your code compiles at all is probably because you have a using namespace std somewhere. (Otherwise vector would have to be std::vector.) That’s something I would advise against and you have just provided a good case why: By accident, your call picks up std::distance(), which takes two iterators and calculates the distance between them. … Read more