Its been a while since I talked about the DSA book but to summarise its had over 20,000 (first, second) downloads which has largely provoked me into taking the whole thing a lot more seriously for the next edition which I expect will triple its content.
I don’t have any times at the moment because we are figuring out what we want to add to the book based on the current programming climate. So, if you have any suggestions then please let me know by emailing me via the contact page. Don’t hold back – what would be your dream book on data structures and algorithms look like? what would you expect it to cover? Does the language independent approach work for you?
Please let me know.
Sorry folks for the lack of posts but ever since I’ve moved to Australia I seem to have had very little time to actually post something of any calibre.
At the moment I am actually working on some writing commitments I have so I will post about them when they appear online. In the meantime I’ve resurrected my Twitter account in a hope to micro-blog more in an effort to make up for my blog shortcomings as of late.
I can’t promise it will be pretty but you are more than welcome to follow my ramblings on Twitter.
I like MSDN I really do but when you want to increase the font size the thing just breaks and looks awful. Recently I’ve found that switching to the loband version of a MSDN page is far better when increasing the font size so its more comfortable to read. Originally I found this suggestion posted by Jon Galloway here.
Definitely helps if you are staring at MSDN for the best part of the day.
I’ve just created a Google group based on the SSCLI which you can view and join by going here – http://groups.google.com/group/microsoft-shared-source-cli
It supersedes now defunct SSCLI newsgroups from the Microsoft and Yahoo servers which have had all but no activity in the last 2 or so years. If you have any interest whatsoever in the SSCLI then I encourage you to join.
The updated version of the Data Structures and Algorithms book that Luca and I wrote is flying out once more! We are really very happy to see how many people are downloading our book. In total (counting the previous release) the book has had nearly 16,000 downloads! Amazing.
If you haven’t already got a copy what are you waiting for?! Its free so you don’t have to reach into those empty pockets at this time of year.
Download the updated version of the Data Structures and Algorithms book here!
Enjoy. Merry Christmas and a Happy New Year.
Just in time for Christmas 😉
You can download a revised version of the book Data Structures and Algorithms: Annotated Reference with Examples here!
The last version of the book has had just under 14,000 downloads since we released it.
Download the book now!
Data Structures and Algorithms: Annotated Reference with Examples
I thought I would share my experiences with Rotor on Vista (x86 and x64). First off Rotor is an open source version of a big chunk of what’s in the full commercial .NET that you use on your machine today BUT certain things in Rotor are no where near the quality of that in the commercial .NET – keep that in mind.
I hacked around with Rotor on several setups not including the supported setup (XP with SP2 and VC++ 8.0). My mileage with each is briefly summarized below.
Vista x64 with VC++ 9.0
I tried to get Rotor working with Vista x64 and VC++ 9.0 but was unsuccessful. Couldn’t even get it to build. This was as I expected though.
Vista x86 with VC++ 9.0
Made the same changes I did with the x64 version pretty much and got it to build. After the initial hope of it all building and the tests that Rotor comes with all passing I was somewhat annoyed that some programs including the C# compiler were not behaving correctly e.g., the C# compiler would give random parser errors for programs. I’m sure that other components were affected as well but seens as though I needed the C# compiler to work this was pretty much the final straw for me.
Vista x86 with VC++ 8.0
Builds without any hacking required. Every now and then though a buffer overrun would occur during the build, particularly when building some of the BCL C# stuff. Haven’t had this error again since I rebuilt my machine but the obvious fix would be to just make the buffer that is overran larger. This occurred during a call to MakeMacroString and it seems as though someone else has come across this as well.
My personal view is that the SSCLI project is doomed to spend the rest of its time only officially supporting that which it did when it was first released. If anyone knows any different then let me know. I couldn’t find any information on the web hinting that it would be updated if only to support Vista.
In a bid to keep up with friends and suchlike I have joined Twitter. I can’t promise much in the way of earth shattering Tweets but I’m sure it will be a mildly entertaining read.
So, if you want to follow me please tune your browsers to this URL – http://twitter.com/g_barnett.
Probably worth noting that the Tweets I make will not necessarily be on .NET. Follow me at your own peril! 😉
One of the great things that came out of the PDC for me was the confirmation that code contracts would be coming to .NET 4.0. I was a big fan of Spec#  but admittedly I never thought it would make it into the mainstream C# or VB.NET languages even though the prior solution provides the more concise and descriptive syntax. On Sunday I played around with the library released at the PDC  and in general it all looks good. For the astute reader you will know that I co-authored a book on Data Structures and Algorithms  with Luca  not so long ago (we will probably release an update just before Christmas, more on that later) and each algorithm within the book states both pre and post conditions. We did consider explicitly defining invariants as well; however we opted not to for conciseness.
While I’m very much encouraged by the inclusion of code contracts in .NET 4.0 I’m still a little apprehensive about it in API form, maybe it’s because I was set on a language based feature set? I’m just not sure.
The big thing here is that there will be something in .NET 4.0 and hopefully its inclusion in the official distribution will emphasise to developers the importance of specifying explicitly contracts to which their algorithms will adhere to. Another interesting thing that came up in the session on code contracts , which coincidentally shared its session with Pex [ 6] was the announcement that there would exist tooling that would analyse the contracts within your code and inject the necessary documentation in there. Whether this will annotate the source code with xml-doc or do something else I’m not sure though. The former was the one most alluded to during the PDC session.
Sorry about not posting recently I’ve just moved to Australia from the UK to do my PhD. Today actually I shared my desk with Gordon Bell  who was visiting the Microsoft QUT eResearch Centre [ 8] of which I am now a member.
1. Mike Barnett, K. Rustan M. Leino, and Wolfram Schulte. The Spec# programming system: An overview. CASSIS . 2004, Vol. 3362.
2. Code Contracts download. Microsoft Research. [Online] 2008. http://research.microsoft.com/research/downloads/details/4ed7dd5f-490b-489e-8ca8-109324279968/details.aspx.
3. DotNetSlackers. [Online] 2008. http://dotnetslackers.com/projects/Data-Structures-And-Algorithms/.
4. Tongo, Luca Del. [Online] http://blogs.ugidotnet.org/WetBlog/Default.aspx.
5. Channel9. [Online] 2008. http://channel9.msdn.com/pdc2008/TL51/.
6. Microsoft Research. [Online] 2008. http://research.microsoft.com/Pex/.
7. Bell, Gordon. [Online] http://research.microsoft.com/~GBell/.
8. Microsoft QUT eResearch Centre. [Online] http://www.mquter.qut.edu.au/.
The 7th part of the design patterns series was published today. This part covers the template pattern.
View it – Design Patterns – Part 7