I've just implemented a compiler that reads a specification file and outputs code that can encode/decode a communication protocol for an on-line game. Sure beats manually making code to for hundreds of packet types. Another advantage is that I can easily add back ends for many languages. Not to mention that using Lisp made the compiler coding fun

Libraries! I just finished modifying a slightly aged bit of code in the CMU AI repository to make Gambol (basic prolog-like functionality).

My current big project is to make my SVG library lively enough to privide basic GUI behaviors. That means I have to learn Javascript and the whole DOM API first. Fortunately, parenscript has made this go more nicely, so far at least.

wm.annis wrote:Libraries! I just finished modifying a slightly aged bit of code in the CMU AI repository to make Gambol (basic prolog-like functionality).

Very cool. Lisp needs some more Prolog-like libraries. I started learning a bit of Prolog the other day, and while I really couldn't see writing a large program only in Prolog, I can see that it would be very handy for solving certain smaller problems within a larger Lisp program. One of the things I love about Lisp is that sexprs are so convenient for expressing things like Prolog within Lisp.

In these few hours, I'm writing a program that will help me manage my tea collection (I keep tea in my own boxes, and I always forget how long I should brew them, what to sweeten them with and so on). Yea, I could just make a list, but where's the fun? I'm also making it modular, so that I can write various frontends to it. I'm not sure why something that tells you how to make your tea should be this big, but what the heck...

I'm currently thinking about doing some experiments with retargetable assemblers, but I'm caught up with a bit of work right now.