Anith Gopal

I just attended to an excellent, excellent Mix 09 session titled “The way of the whiteboard”; its fundamental premise is that a picture is worth a thousand words.

Our blog editors have just received unconfirmed reports that the .NET Micro Framework team might be on the verge of launching a comprehensive “partner program”. Businesses selected in this program are expected to receive a wide variety of promotional and co-marketing benefits from Microsoft.

  A very common pattern in the usage of managed exception handling is that of catching an exception, inspecting it’s type and rethrowing it once you realize it was not the exception you wanted to handle. Below is such an example (and should be avoided in preference to another approach described further below in the writeup) that uses CustomBaseException as the base type of an exception hierarchy and CustomDontWantToCatchException as a type that derives from the base class that you wouldn’t want to catch:       private static void Foo()     {         try         {             // Set some program state             // Do some work that can possibly throw an exception         }         finally         {             // Reset the program state         }     }        public static void Main()     {         try         {             Foo();         }         catch (CustomBaseException ex)         {             if (ex is CustomDontWantToCatchException)                 throw; // Rethrow since we dont want to handle exceptions we aren’t interested in!             else             {                 // handle the exception             }         }     }   Managed exception handling comprises of two passes:   1.

I will demonstrate here how we can use the functional programming feature in C# to program something like a statement/expression translation.