Here’s another portion of the video interview that I shot over Christmas at Coverity headquarters in San Francisco.
In this bit I talk about the history of C#, how C#’s safety system is definitely a step in the right direction but not by any means a panacea, the most common defect patterns we find in C# code, the basic workflow for using the Coverity static analyzer, and finally a plug for this very blog. That’s a lot to fit into seven minutes!
Today on the Coverity Development Testing Blog‘s continuing series Ask The Bug Guys, I answer a question I get quite frequently: what guarantees do we have about object disposal when the body of a
using block is interrupted by an exception? The situation is rather complicated, it turns out.
As always, if you have questions about a bug you’ve found in a C, C++, C# or Java program that you think would make a good episode of ATBG, please send your question along with a small reproducer of the problem to
TheBugGuys@Coverity.com. We cannot promise to answer every question or solve every problem, but we’ll take a selection of the best questions that we can answer and address them on the dev testing blog every couple of weeks.
Someone at Reuters is having too much fun:
China threatens drama
meets the Dalai Lama
meets the Dalai Lama
despite China drama
I am reminded of the immortal words of Ogden Nash:
The one-L lama, he’s a priest
The two-L llama, he’s a beast
And I would bet a silk pajama
There isn’t any three-L lllama
To which my Bostonian friend Marty responds “that big fire was a right three-alahmah”.
The nice people at DevProConnections asked me to write a beginner-level article for them about the perils of arithmetic in C#; of course these same perils apply to C, C++, Java and many, many other languages. Check it out!
Thanks to everyone who came out to the on-the-web and in-person events last week; it was an exhausting week but I had a great time. I’ll post the links to the recorded versions of the talks once I have them.
Developer Tech was kind enough to ask me to write a few words about the past, present and future of C#; this article is mostly pitched at people unfamiliar with the history of the language. If you read this blog you probably know all this already, but if you want to check it out, the article is here: http://www.developer-tech.com/news/2014/jan/30/past-present-and-future-c/