Older blog entries for tromey (starting at number 8)

Lately I've done a ton of Classpath/libgcj merging. That's easy and makes me feel like I'm making progress. Also I wrote the assert feature for gcj -- I always make some nice progress on a self-contained project like this when I'm on a trip.

I saw a few movies lately:

  • The Importance of Being Earnest. Enjoyable, though in the end it was missing some emotional punch. Still, I recommend it, if only to watch Colin Firth prance around.

  • The Bourne Identity. There's an obvious Unix parody to be written here. The shell forgets its identity, acquires features, re-emerges as bash or zsh. Something like that. Anyway, for an action flick (I usually practice genre-relative reviewing) this was pretty good. It exceeded my expectations, which were quite low.

  • Attack of the Clones. Not as bad as number 1.

  • About a Boy. This was pretty good, but still missing something. Also I found the character development a bit trite.

  • Sleeper. I saw this at the outdoor theater here, which is always fun.

  • Monsoon Wedding. Loved it. Though Elyn pointed out that if it were an American film, I would hate it for espousing traditional values. Still, the energy and flair were there.

  • Scotland, PA. A sometimes funny take on MacBeth, set in Pennsylvania of the 1970s. In the end I don't really enjoy cultural parodies like this. Plus, for me the real greatness of Shakespeare comes in his language, not his plots, and this version rewrote the script.

26 Apr 2002 (updated 29 Apr 2002 at 00:45 UTC) »

Yesterday I checked in what I hope is the last bug fix for gcj for the 3.1 release. That's a relief; on to new things.

Last night I saw a movie called American Astronaut. It is a musical comedy space opera western. More or less. It is one of the strangest movies I've seen in quite a while. I recommend it if you're feeling a bit silly and don't mind low-budget indie movies. It was inventive and enjoyable.

Another couple weeks spent on gcc 3.1. Luckily, this is going to end soon. Today I worked on what I think is the last critical gcj bug for this release.

We have a bit of a problem in gcj, which is that only two people (Alex and Per) are familiar with the front end, and only Alex is really familiar with certain parts. They're both apparently pretty busy with non-gcj stuff, which means that compiler problems go unfixed, patches go unreviewed, etc. Somebody needs to step up here. Maybe me.

I've been looking at Gnome again a bit. Today for fun I wrote a little gnome-session patch. It's pretty silly. I've also been looking at GStreamer, which looks quite nice. The documentation is pretty good overall, but there are still some important missing pieces.

I've been working on gcj 3.1 pretty much full time. Don't these entries get boring?

One thing I've noticed is that saying the words "upcoming release" acts much like chumming for sharks. Suddenly all these bugs I've never heard of appear, and suddenly lots of platforms that ordinarily never see patches start getting three or four a day. Keeping up with this is taxing.

It makes me wonder if there isn't something better we can do. Currently I'm leaning towards just incremental improvements: writing more tests, more documentation, having nightly regressions on more platforms. These things would at least let us know when we broke something that used to work.

Today I took a break from gcj 3.1 release work and replied to some Automake email. I also did some AWT hacking; most of the TestAWT application works with gcj now. The hardest thing is finding relatively simple AWT applications so I can test it.

I've been continuing to work on gcj 3.1. Things are coming along nicely. This is going to be an excellent release for us.

Last night I also did a little bit of work on Automake. We'll release 1.6.1, a bug-fix release, as soon as we fix the major bugs found in 1.6.

Today I read the guest essay on linuxandmain.com by Shawn Gordon. He argues against using the GPL. Now, he might have a good reason, but his examples and other supporting arguments really aren't very good. I'm not linking to it since really it isn't worth reading -- it isn't a serious essay.

Last night I gave a talk on autoconf, automake, and libtool at the local LUG. It went pretty well, I think, especially given how nervous I was at the start.

Lately I've been working on getting gcj 3.1 ready for release. You can see the status.

The gcc 3.1 release is coming up soon, and gcj isn't quite ready. I spent today making a list of release-critical bugs. I fixed a couple of the problems. 3.1 is going to be the best gcj release yet: we have much better library coverage (still no AWT -- probably 3.2), better performance, and the interpreter works on more platforms.

Today I hacked on the Classpath Gtk+ AWT peers. AWT is the biggest missing piece of libgcj, and I'm pretty interested in having it all work.

I also spent a little time looking at my Emacs TAGS patch. This patch changes the TAGS file format a little so that the command line used to create an entry is recorded. It also adds some code to etags.el so that when you save a buffer, the TAGS file is automatically updated. No more make tags.

Finally I worked on my automake slide show a little. I'm giving a talk at the LUG this week and I need some sort of visual outline.

New Advogato Features

New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.

Keep up with the latest Advogato features by reading the Advogato status blog.

If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!