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
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
Dispose method for transaction class performs a rollback while Oracle’s class doesn’t. So from transaction’s perspective it’s implementation dependent. The using statement for the connection object on the other hand would either close the connection to the database or return the connection to the pool after resetting it. In either case, the outstanding transactions should … Read more
From MSDN, using Statement (C# Reference) The using statement ensures that Dispose is called even if an exception occurs while you are calling methods on the object. You can achieve the same result by putting the object inside a try block and then calling Dispose in a finally block; in fact, this is how the … Read more
No. The compiler will generate a separate finally block for each variable. The spec (ยง8.13) says: When a resource-acquisition takes the form of a local-variable-declaration, it is possible to acquire multiple resources of a given type. A using statement of the form using (ResourceType r1 = e1, r2 = e2, …, rN = eN) statement … Read more
Yes, that should be fine. In the first case, you’re really saying: Asynchronously wait until we can get the response Use it and dispose of it immediately In the second case, you’re saying: Asynchronously wait until we can get the response Asynchronously wait until we’ve logged the response Dispose of the response A using statement … Read more