User login
DMD release process
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.
Since we're all part of a community, I think it would be easy enough for Walter to send a release candidate to a few persons and ask them to test it on the larger projects in the D world. Off the top of my head, I would suggest Tango, ArcLib, MiniD and DWT as important starting points.
This has been suggested before though, without anything happening, so I'm not really sure that Walter likes the idea.
Technorati Tags: I am of course biased, but
I am of course biased, but for those deciding to use D, the competing standard library issue seems to be of little problem, except possibly for those deciding to switch after having used the other for some time. This would have been a bigger problem if both libraries were of mediocre quality, but Tango is definately of very high quality.
As for version control, Phobos is there now, so there is hope that Walter will get to it for the compiler too. Indeed, I believe he has said that has an intention to go there at some point.
Ye, rite!
*cough* bullshit *couch*
Not that I don't think you're biased - claiming that Tango is of "very high quality" and blaming everything on DMD certainly shows your how biased you really are.
I agree that DMD hasn't been reknown for its stability, but the alternative, GDC, doesn't fare any better. Tango is a chapter of its own - beeing constantly a moving target doesn't inspire stability either.
First, my post is about
First, my post is about regressions in the compiler, and how that affects unchanged code in Tango.
Secondly, quality of code have nothing to do with changes in API. If anything, changes is an admittance that Tango certainly isn't perfect and can be further improved. Tango 1.0 will be stable.
As for GDC, sure - one can always call it stable, but that is because it hasn't had a release in one year, and that release is not usable with Tango as mentioned in the download pages. Tango provides a recent snapshot for download in that case, and GDC has througout various SVN revisions actually been a whole lot more stable than DMD, although that picture is a bit skewed as GDC uses the DMD frontend, and Tango is made to work with DMD when new stuff is merged into GDC.
Search
Browse archives
| Mo | Tu | We | Th | Fr | Sa | Su |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 |
For people investigating the
For people investigating the D programming language, the dissatisfaction with compiler quality and the release process from the authors/managers of one of the two competing standard libraries (another glaring issue...) doesn't settle well.
Walter really needs to get with the program and make his development repository available for read only access. This is probably difficult for Walter considering that he hasn't fully embraced open source. It wouldn't surprise me if he doesn't use version control, either. Maybe he needs a smack upside the head with the DVCS cluestick. Get him to start using git/mercurial/arch/bazarr/monotone/whatever, and publish a repository so his community can track the changes.
Otherwise the perceived instability of the compiler and the competing standard libraries are going to relegate D to the language backwater where it'll just be a geek curiosity.