My workplace just gave me permission to open-source two projects I did for them. One is screen-scraper, a rudimentary (but extensible) vt100 terminal emulator for lisp (BSD licence, sans advertising). The other is debian-security-updates, a netsaint/nagios plugin and debian security update SNMP agent adaptor (GPL).
Wow. Lots of nouns in that last sentence.
Just returned from watching Udo 77, the musical about Udo Proksch (here’s the monochrom blog entry with some background information on him).
Much fun was had by all (including the actors!). Key highlights: a gay love story between two computer programs (singing a love song in english, though), really pretty good music, sarcastic technobabble that was funny even if you know a bit about computers. No lisp, though.
So, the obligatory lisp content in this journal entry.
Lisp content first: I added a few features to the SBCL auto-benchmarker: When it encounters compile errors in the last revision, it sends an irritating mail to sbcl-devel (currently, to me, so that I can test and extend the auto-irritation levels a bit more).
Right. And now for some real-world stuff. There is now a Picture album online, which is semi-automatically updated from my digicam. Included are a few shots of our mouldy toilet.
Greetings from room TD11 at ENSERB at Bordeaux University. currently discussing possible buffer abstractions for a properly protocolized cl-emacs. More details later (and pictures, I forgot my camera in my hotel room today).
See The SBCL pages (you might also notice the link in the top navigation bar). The Benchmark runner needs to automatically build every SBCL revision, anyway. It could build the manual, as well. And so it does.
A google search for Lisp tutorials often doesn’t yield a useful result for a newbie: Lots of Tutorials from the late 90s and 80s. Most call it “LISP” (in capitals), and refer to “the interpreter”. This does not reflect reality any more. Here are some more useful introductions to Common Lisp:
Learning Lisp, the #lisp yabo way Practical Common Lisp: upcoming book on CL by Peter Seibel. - highly recommended.
…what it means when people say that a thing is “rock solid” (especially when they speak of security). It means that they never tried to break it.
I released a new version of iterate today. It fixes a bug in synonym code, removes spurious WARNINGs on perfectly good code, and adds a README (the same as the iterate page) and a BUGS file (find the current version on the iterate bugs page). Get it at http://boinkor.net/lisp/iterate/iterate-current.tar.gz. The signature is at http://boinkor.net/lisp/iterate/iterate-current.tar.gz.asc.
Welcome, visitor. Now that the atom feed is (mostly) working, and there is some content on this site, I think I can upload it without too much of a bad conscience. When more content becomes available, I’ll link it from here.
A technicality, though: Permanently valid links into this journal don’t work yet. I’m trying to work something out.
Alright, I seem to have finished the atom feed exporter. The whole thing is less painful than I thought. Check out the shiny button:
clicking should tell you that this is a valid feed.
Haha. Of course, the atom button invalidates the feed because muse’s html generator doesn’t insert </P> tags everywhere it should - and it doesn’t yet escape > and < correctly. But for now, this will work well enough.