Unit Testing, Agile Development, Leadership & .NET - By Roy Osherove
Making your api free of side effects is one of the best things you can do. This means that you can use the API without constructing any special purpose objects (e.g., all methods are static within the API wrapper class).
#1 on the VB list is quite limiting in the C# space, if you're trying to do language-oriented programming/internal DSLs. I had a request come up in an OSS project I'm on, and my answer was "wait for VB10".
Since VB10 has _real_ lambda support, why cripple your API now just to un-cripple it when VS2010 ships? The Action delegates are a big deal for internal DSLs, I shouldn't be forced to make _every_ _single_ callback parameter return a value, especially if I'm designing grammar paths.
The VB team made a design mistake, which they are fixing in the next version. I would suggest designing your Isolator API such that whatever "fixes" you put in for VB devs is easily obsolete-d in the future.
I agree with Jim. Not only missing lambda is coming in VB10, most of developers that focus on their products (unless they also design API for other developers) don't care at all if the API they use has a counterpart in other languages.
Pingback from C# test.net » API Design Values
Pingback from Development and Integrity Management by Eli Lopian » Why do we ignore your arguments?