It looks like I may have jumped the gun with my conclusions from the previous exercise to benchmark string performance in Delphi 2009. Following a useful exchange in the comments with Kryvich I corrected a small discrepancy in the tests and made some changes to the performance testing subsystem within the SmokeTest framework. I then re-ran my string performance benchmarks with some significant – and more encouraging – differences in the results.
Just a short post this one. Somebody else may already have mentioned this, but I only just figured it out for myself – the CompilerVersion for the Delphi 2009 compiler is not what you might expect (and is not what the documentation says it is!). Both CompilerVersion and RTLVersion have the value 20 in Delphi 2009. In Delphi 2007 these were 18.5 and 18.0 respectively. Confusingly the documentation is correct for RTLVersion but incorrectly gives 18.0 as the value for CompilerVersion. Is anyone else wondering what happened to 19? Did Delphi 2008 happen after all and I just missed it?
Prompted by a conversation with some colleagues where-in we collectively speculated about the implementation details of a generic class and what impact – if any – this might have on performance vs a “traditional” polymorphic equivalent, I threw together a quick performance test case in my Smoketest framework, and as a result discovered a couple of significant changes in Delphi 2009 that created some unexpected problems.
I imagine the news has spread like wildfire – the Delphi 2009 Trial Edition is now available for download! I got me one, and these are my initial impressions.
Since I’m preparing a series of posts about (and eventual publication of) Smoketest, my own testing framework, I thought I’d test the water with this weeks poll and see what – if anything – people are already using as far as unit testing goes. Also I thought I’d briefly mention that I am at Microsoft Tech Ed ’08 (NZ) this week, and it was good to see that the NZ CodeGear reseller, Developer’s Inc were handling a steady stream of traffic at their stand where Delphi 2009 was on display (in the form of data sheets :)). I asked when Delphi 2009 was expected to ship and was told that it had been released to manufacturing and was on target to start shipping on 20th September – I forgot to ask whether that was an NZ date or worldwide. Not quite from the horses mouth, but pretty darn close. 🙂
With Delphi 2009 literally just around the corner, I thought it would be interesting to see how it’s impending release is being viewed. As a result, the poll answers are a little wordy this week for which I apologise, but I thought it would be interesting to try and gauge a detailed view of how people view the new version and how it will impact them.
eWeek have a detailed article with quotes, attributions and pricing in which they state an August 25th (next Monday, by my reckoning) release date for Delphi and C++ Builder 2009! The Delphi blog-sphere is probably going to go into meltdown with this news and speculation as to whether it is accurate or not. The indications were that the release wasn’t far off, but it’s much sooner than I think many were expecting, myself included. I am also somewhat surprised that we didn’t hear about it first from CodeGear directly, certainly confirmation (or clarification) now is quickly needed.
One control that I have not seen in the line-up of new controls in the VCL for Tiburón is a size grip. Most people may not even realise that this control exists, even though it is part of Windows itself and is really quite useful. Fortunately, implementing it ourselves is truly trivial.
I was a little disappointed that the preview webinar this morning was little more than a re-run of the same content from a little over a week ago, albeit with some downloadable PowerPoint slides this time. It was at least an opportunity for some more Q&A and a couple of interesting Q’s got A’d.
Providing a little light relief after the rather heavy series of posts on multicast events, a colleague recently asked me what Tiburón actually means. So I looked it up. As well as being a town in California, it is also Spanish for shark. I don’t know which derivation inspired the team at CodeGear, but it does raise the possibility that here in Aotearoa we could perhaps be referring to the forthcoming release of Delphi as Mangō, as this is the Maori for “shark”. Some additional trivia – from the little that I have picked up of the Maori language, “nui” in a name implies “big” or “large”, so the place name Mangonui (which crops up in a few places here) means “big shark”.