larsivi

As have already been noted on D.announce, I have started committing new code to DDBI. The task at hand is to refine the interfaces, make it easier to use where possible, and use as little resources as possible (this isn't necessarily easy given that fetched data need to stay in memory somewhere).

I have committed some new interfaces in dbi/model/ and implemented those (mostly at least) for mysql. SQLite will be the next to be added, and after that maybe PostgreSQL. I expect to have to rely on contributions for anything beyond that.

If you have any thoughts on the work I've been doing, please contact me. My current thoughts involve adding multi statement/multi result support (thanks BCS), make sure optional allocators can be used properly (and in all places applicable), how to best fetch results and error handling.

I'm to some degree active on LinkedIn and my answer to a question there led to the quotes that can be found in this article. Although the name isn't mentioned, my quotes are all taken from my work on Tango.

The article is about how easy/difficult it is to write/use open source software on Macs. Although I am fully behind my quotes there, she did leave out the ones that weren't so negative.

After the previous post on the topic, I have received quite a few followers on Twitter (15?) and 2 on Ohloh. I guess this means that I will use Twitter most, but I may duplicate what I consider important D/Tango messages to Ohloh, just to make it appear somewhat active there too (The Ohloh page takes its time updating the stats, so it gets kinda static without some other activity).

As for the Hackontest competition, they will start the selection process on August 1st. Apparently only 6 projects fulfill the requirements and are thus eligable. Tango isn't one of them, but is pretty close (missing one implementor).

Seems like it isn't all to long since last time I wrote about the D compilers - then about quality. This time I'd like to write about DMD's release process, as it is highly frustrating for me trying to have Tango compile with it.

Almost every release sees a regression, or some obscure accepts-invalid bug getting fixed in what is meant to be the stable branch. Today DMD 1.032 was released, with at least 3 issues causing immediate harm to Tango. One I made go away in SVN, but I'm considering reverting, and just calling 1.032 broken. The last 2 issues I don't know how they affect Tango yet. Actually, there may even be more that I just didn't get to yet.

I recently got my self a twitter account, and not very surprisingly you can find it at http://twitter.com/larsivi. The reasoning behind the move is that I don't want to post too much low quality content to this blog, and thus I end up seldomly really having to time to write here. With twitter I can make short notes and anecdotes without worrying about quality.

I'm not normally interested in the daily dealings of all people around the world, but see Twitter as an easy way to post thoughts around the open source work I do, and a bit of software development in general. Considering this, I think I find Ohloh's journals a better idea (or a better match towards what I want), but I'm not sure many enough of the D users use Ohloh to make the feature work for me. Also, Twitter could spread the "word" wider, although I guess the "word" would be considered less interesting to most potential readers.

A few weeks ago, I entered Tango as a project for the Hackontest - a 24 hour hacking contest for 3 select features for various open source projects. The hacking will be done by teams of 3. For those attending, there will be cash prizes and most likely an exciting trip to Zurich, Switzerland.

Now, the catch is that a jury will select the 3 projects/features that will be part of the competition proper, and these will be chosen from those entered at the site linked further up.

When I registered Tango, there was a

KeYeR (Piotr) called upon me in #D and said that my statement "This is one of the worse decisions among the bad ones in the D history." was bad English. No, not really. He said that it was a strong statement, and sure, it is. I tend to be (unnecessarily so?) strong in my rather few statements on design choices in the D language. Peter added that he was afraid that I was right.

As I see it, Walter here is willingly implementing a solution that 99% of the community seems to hate. He even had a different implementation, the manifest keyword, that was applauded

When I talked about the three T's, the last one stood for TODO. Well, in the Tango world, i probably should have made that Ticket. Since our latest release, the reactions have been relaxed, mostly due to the holidays I guess (and partially because the contents were well known). Only 9 tickets have been created since then, and at least 5 of them were web and documentation related. The web part is natural, as I redid the layout of the Tango frontpage, hopefully for the much better (at least visually, I believe we could do it in a more proper styles based manner, please join us if you think so). I think the tickets related to this change were all resolved.

As for the docs, one ticket was about private members in the DDoc output. Now, this is easily removed by changing the style of the source code comments, but do anyone know if this is

We just released the next version of Tango, 0.99.1, which is mostly a bugfix release. To the Tango team, events surrounding it are encouraging though, as they show that Tango gains more users and more compatible libraries.

In addition to the compression stream filters by Daniel Keep, many of the bugfixes in this release, were due to patches and suggestions by users. As such, one bug in the collections package was reported 4 times over a

From time to time, Walter says that we need to do things that will increase the visibility of D outside of the D community. Each little effort is in itself probably too small for a noticable effect, but over time and with many such efforts, we make a difference.

I try to take every opportunity, both because I want D to succeed, but also because I want to succeed in having D programming as my main source of income. Of course, when I discuss and plug D, I usally