Delphi 2005 Update 1

Merry Christmas... or as my son likes to say, “Happy ChrismaHanniKwanzica” :-)... Anyway, the Delphi 2005 Update 1 is now out.  You can get it from the registered users site.  This should address a lot of the various memory consumption issues some folks were encountering.  We do potentially have a second update in the pipeline, however the timeline for that has not been established.  With the release of C++Builder open letter, a lot of our schedules are in a state of flux at this point.  Once the holidays are behind us, we will be able to truly begin to nail down the plans and schedules.  .NET 2.0 is on the horizon and is a very important release for us as well.  We can ill afford to derail that effort, so careful planning an consideration has to take place.

Delphi 8 Update 3 now available

It is listed as a “public beta” for now.  It is available by following this link to the Borland Developer Network.  Be sure to read the article as this is a breaking DCU change, which means that if you have components for D8 for which you have no source, you will need to go back to the supplier to get an updated set of binaries.

"Who's on first" and MS Support...

Seems my post about calling MS tech support has been compared with the old Abbott and Costello “Who's on first” comedy routine.  While that old comedy routine is certainly one of my all time favorite bits (in fact, I chuckle each time I even think about it ;-), I don't think that my post is even in the same league.  Abbott and Costello are true comedic legends.  I'm just some dude at a software company...with a mild sense of humor.

My take... The Borland C++Builder Open Letter

The Borland C++Builder Open Letter

It's here and was posted a day early.  So far the reaction seems to be one of guarded optimism.  Not surprising, really, given all that has transpired for the last couple of years on the C++ front.  For me, personally, this is exciting news.  This is an opportunity to once again work with some folks for which I have a ton of respect. 

Internally, we've all been lobbying (dare I say, pleading ;-) with management to take this step.  We, on the Delphi team, have always held a certain kinship with the C++Builder community, and for good reason;  We've gone through at least four release cycles together, wrestled with binary compatibility and even benefitted from each other's innovations.  In fact, the initial driving force behind the rearchitecting of the IDE into the Galileo codebase was because of the desire to eventually merge the Delphi and C++Builder products into a single, simultaneously shipped, unified environment.  It was not Delphi for .NET or C#Builder that sparked that effort, but C++Builder.

Of course I cannot comment with any more detail than was revealed in the open letter... mainly because, quite honestly, we don't actually know yet.  We are in the midst of planning, scoping, and scheduling the next release of Delphi, in conjuction with the C++Builder team to create a common roadmap.  Whether or not there is an off-ramp on that roapmap for a release of C++Builder sooner than the next Delphi release is currently an unknown.

Hmm... it's a good thing we kept all that C++Builder code warm and on “hot standby” within the Delphi codebase ;-)...  So bring out the fatted calf, prepare the feast!  The prodigal son has returned!

Cool Stuff.

Chris Hesik has some great information about using the debugger in Delphi.  Check out this post on how to manually walk the stack.  Great stuff.