Disposing issue
in [CSharp]
|
From: Peter Duniho on 4 Feb 2010 12:23 Mr. Arnold wrote: > Well, I am going to standby my claim about it. One shoe doesn't fit all > situations. The Using statement is suspect. Prove it. Post an example that doesn't work. > [...] > I am not testing anything, as I have already seen the Using statement > not do what it's suppose to do, and I find it suspect. You've never seen that the "using" statement doesn't do what it's supposed to do. > Yeah, I fixed the problem by getting rid of the Using statement period. You may have rearranged the code, and in doing so may have removed YOUR bug that was causing problems. But merely changing from a "using" statement to the equivalent "try/finally" did not fix any problem. > I am not buying it, and the Using statement doesn't work as advertised > 100% of the time. It works exactly as advertised, 100% of the time. Pete
From: Peter Duniho on 4 Feb 2010 12:45 Mr. Arnold wrote: > Peter Duniho wrote: > > <snipped> > > What I see here Peter, if someone says anything that disagrees with you, > or is somehow detrimental to MS on an area, then the moderators will > block reading of the post. That's real good man real good. It's damage > control I guess, as seen by the same tactics being used in the MS Vista > forums. Oh, yeah. Microsoft's got my back. Don't dispute anything I write, or else you'll be censored! Uh, right. That's why all the other disagreements with me, including your own, remain. I had to check Google Groups to see what the fuss was about, since I didn't see the original post on the Microsoft server. And yes, while I didn't find the statement threatening (seems like an obvious � hackneyed even � pop culture reference to me), I can see how it might be considered by Microsoft to have crossed the line. In response to the specific claims you made though: � If there's a problem, it can be demonstrated without showing the exact code in which you found it, proprietary, confidential, or otherwise. Just create a specific proof-of-concept, concise-but-complete code example that reliably demonstrates the problem. Not that you'll be able to to. But that would be the way to prove your case. � You claimed that using "try/finally" instead of "using" is a "Best Practices for Web Performance" recommendation. Well, I entered that phrase in Google, and the only examples of it are from your own post. I'm sure that there's no Microsoft statement that recommends "try/finally" instead of "using" as a way of improving performance. But please feel free to post a link to some reference that you think provides that recommendation; I'll be happy to look through it and see if it really says that. Most likely, you've simply misunderstood some other statement. Of course, even a recommendation to use "try/finally" instead of "using" for performance would have nothing to do with _correctness_, which is where you claim the "using" statement fails. But in either case, since all that "using" does is cause the compiler to emit exactly the "try/finally" code you'd write by hand, it's implausible that there would be either a correctness or performance difference between the two. Pete
From: Mr. Arnold on 4 Feb 2010 13:06 Peter Duniho wrote: <snipped> I am tired of you Jesus.
From: Peter Duniho on 4 Feb 2010 13:26 Mr. Arnold wrote: > Peter Duniho wrote: > > <snipped> > > I am tired of you Jesus. So, in other words, when asked to "put up or shut up", you choose the latter. Got it. Glad we could work this out.
From: Mr. Arnold on 4 Feb 2010 13:53
Peter Duniho wrote: > Mr. Arnold wrote: >> Peter Duniho wrote: >> >> <snipped> >> >> I am tired of you Jesus. > > So, in other words, when asked to "put up or shut up", you choose the > latter. > > Got it. Glad we could work this out. I am going to tell you again dummy. It's code owned by the DoD, and I am not posting it. And besides stupid, I haven been posting from home for the last couple of days after getting out of the hospital this past Monday, Jesus. |