F# 1.1.7.0 available and other stuff
Dr. Don Syme and the F# team have released F# 1.1.7.0. While the release number has gone from 1.1.5.2 to 1.1.7.0, indicating that this is a minor release, there are a few items of note.
The source for ILX, Abstract IL and the F# compiler are now included in the the distribution. Ummmmmmmmmm, that's all of the source code for that stuff. In other words, if you'd like to see the work of one of the premier computer scientists at Microsoft Research and the code for much of the collateral to construct a language in .NET, here it is.
Dr. Syme had hinted that his next undertaking in F# would be to provide examples and further integration of LINQ with F#. There is a sample project, FLinq, but I've been unable to get it to compile at this point and rather than air my dirty laundry here, I'll be taking a moment to contact the F# team (through standard bug reporting - fsbugs (( a t )) microsoft.com) and work through any issues that I have. It is likely "nut behind the wheel" syndrome, i.e. I've gone and done something silly (cue the Three Stooges, Hey Moe, did you perform a proper uninstall of 1.1.5.2?).
Finally, in this distribution, there is expression lifting. I have not had a chance to really review this, but the FLinq sample has countless examples of this usage. It appears to be "late" expression evaluation. If this is similar to features in Mathematica or S-Plus, then this will definitely provide for some useful constructs within my work. Again I claim ignorance until further time is spent in the usage of this feature. Ok, I'm a slowpoke on some of this stuff.
Another milestone for the F# team, and a maturation milestone it is, is the introduction of the F# Library Documentation at MSR. You can find the top page for this repository here and Dr. Syme introduces it here. Syme, Pickering and Margetson have put forward a professional view of this language and I look forward to watching this grow and change as well. It is important to note that Pickering's work with NDoc and F# here, provided a foundation and direction to get this new documentation published. While I'm a fan of NDoc and use it regularly in my work, I agree with the F# Team's decision to provide for a template, while similar to the standard documentation of NDoc (and MSDN and other documenation repositories), that is distinct and will allow for focus on the language as distinguished from other .NET languages. It is still a new documentation repository, but already has useful information on many of the key elements of the language. Along with Pickering's F# Wiki (with apparently numerous contributors), the F# public resources are improving. This represents a clear step forward for the F# platform and I appreciate the hard work of the F# team and all involved, so - thank you to all involved in this work.
On a similar note, the very decision to move away from NDoc and the C# documentation style is in some ways similar to an issue that I am working through. I am a HEAVY user of FxCop (for .NET v1.1 and .NET v2.0) and believe that the source code does convey much of the work, thoughts and ideas of those involved in software construction. FxCop provides for rules that allow enforced quality in the target assemblies of an application. I've tried using FxCop with limited success on F#, i.e. naming rules (among many issues) are different and distinct from other languages. Changes to this would require the construction of new FxCop Rules. This is on my list for projects to provide for Proof of Concept, but at this point is not of high priority. As the base of code in F# increases in my work, the automation of these types of task, i.e. proactive software quality improvements, will receive more attention.
As always, links to F# sites of note are on my blogroll.
As for me, I have now included on my blogroll, a new section for articles. I guess I better start contributing to community a little bit here, especially with the work that I've been doing in F#. The first link in the articles list is Platforms for Development. As I do a lot of development (like all good geeks), I take pride in management of my development collateral. I have a significant number of Virtual PC images that I use for my work. This article describes the platforms which are needed for upcoming articles and are the basis for some of the work that I do.
Oh yeah, The Liz and I are both doing well, thanks for asking. No accidents for this sometimes crazy, female, teenage driver. And a belated Happy New Year, I suppose is in order as well. May you resolve to improve that which is in need of improvement and find success in doing so.
---
As always, contact me here.