As momentum builds for the F# release with Visual Studio 2010, so too does the number of people blogging about the language.  This week we have a spec update, clarified comparisons, decision trees, porting gotchas and in depth explorations of the debug IL generated by F#.  Please do enjoy.   Speaking on F# at the Connecticut .NET ...

There has been a huge spike in the number of F# posts over this past couple of weeks.  For this post I have chosen those I think are most important for the experienced F# programmer to read.  This week we have Common mistakes, the inner workings of Printf, the dangers of null types, and my personal favorite: a Lisp compiler in ...

A few weeks off left me with renewed vigor.  This week we have some very interesting posts on reflective and reactive programming, enhancing F# by adding additional operators, IL analysis via simulation and finally, observations on the productization of F#.   Luke Hoban’s Lang.NET presentation on the productization of F# A set of ...

Some interesting gems this week.  Revit, Closures and MathTools won the day.  However, I do hope you'll take a look at the IL post as well.  Blog – Jeremy Tammik’s Use F# Directly in Revit In Jeremy’s post he discusses what is initially necessary to get F# and Revit working together.  He also provides a sample of a Revit ...

After my last post, A Safe and Asynchronous One to Many Stream Copy Through IL and Inheritance”, I ordered a few books and spent some time playing with generating IL. Along the way I’ve developed a library which allows you to make a franken-clone of any object. You pass the method an object to clone along with a hash table of values to change, ...

Because .NET Streams have state, they are difficult to use in multithreaded environments. In this post I discuss ways to manage or work around problems arising from the statefulness of .NET Streams. I explain how this is possible both through traditional inheritance and also through some indulgence in hacking of object protection levels by ...

After my last blog post, due to some of the responses, I decided to spend some time with Smalltalk.  As a DotNET developer by trade, I wanted to see what kinds of options were available for use on the CLR.  Unfortunately, out of the five different DotNET Smalltalk flavors that have been created, not a single one is still under ...

One of the most often cited reasons to not use .NET is that it is initially compiled to an intermediary language (MSIL) and has to be recompiled every time you run it. In many high performance environments this wasted time is simply unacceptable. To combat this Microsoft released a tool with .NET 1.1 called NGen (Native Image Generator) which ...