Kvardek Du

Illustrating SBCL's build process

2009-06-24T20:41:00.005+01:00

A while back I read Christophe Rhodes's paper “SBCL: A Sanely-Bootstrappable Common Lisp” which describes SBCL's bootstrap procedures.

The paper includes a bunch of diagrams for each build stage. These were pretty helpful in improving my understanding of the build process. So, I tried to take them a step further and create a single diagram that provides a global overview of the build process:

I'm interested in hearing any comments you might have. If you already know how the build process works, does it make you cringe? If you are vaguely familiar with (parts of) the process, does it provide you with some sort of new insight? Given that I haven't included a legend, does it make any sense at all?

Tobias Rittweiller's SLIME talk

2008-12-06T13:34:00.004Z

Tobias has posted the slides from his SLIME talk at a recent Munich Lisp Group meeting. Besides presenting a nice overview of SLIME's internals and features, it includes a bunch of useful tips and tricks.

For instance, did you know that you can recompile a frame with higher debug settings right from the debugger? Or that, after changing some macro in your code, you can recompile all functions that use it with just a few keystrokes?

Lisp at Stack Overflow

2008-09-16T18:42:00.007+01:00

Stack Overflow is a new programming-oriented Q&A website recently launched by well-known bloggers Jeff Atwood and Joel Spolsky.

So far, there's only a handful Lisp-related questions with a couple of answers, some better than others.

I hate web forums as much as the next guy. Long live comp.lang.lisp and all that. However, it's not really just a web forum; it features Reddit/Digg-like voting mechanism and wiki-style editing and it might be a good way of building a (better) Lisp FAQ of sorts, collaboratively. Seems worth a try.

Internacia Konferenco de Fizik-Studentoj 2008

2008-08-20T14:50:00.009+01:00

Ĉi-somere mi ne partoprenis Esperantan konferencon. Anstataŭe, mi vojaĝis al Pollando por la Internacia Konferenco por Fizik-Studentoj en Krakovo (ICPS 2008), kvankam mi fakte ne studas fizikon.

Utilis ke mi partoprenis IJK-on 2006 en Sarajevo ĉar estas kelkaj vortoj similaj inter la pola kaj la bosna lingvoj, pivo kaj piwo (biero), interalie. Mi ne lernis multe pli ol simplaj vortoj, sed mi lernis iomete pri la kompleksa pola alfabeto kaj amuziĝis legante hazardajn vortojn ĉe la stratoj.

Kvankam ĉi tiaj konferencoj temas precipe pri festumado, la oficiala temo estis fiziko. Kelkaj prelegoj estis tre interesaj, kvankam mi ne komprenis amason da aferoj. Mi venis hejmen kun la volo lerni iomete pli pri fiziko, tamen.

Estis ankaŭ alia grava simileco inter la du konferencoj: ambaŭ havis tre internaciajn etosojn. (Fakte, IKFS-partoprenintoj venis el pli da landoj ol IJK-partoprenintoj, mi kredas, kvankam la plejmulto venis el Eŭropaj landoj, en ambaŭ kazoj.) Sed, la oficiala lingvo estis, kompreneble, la angla kaj mi bone sentis kelkajn aspektojn de tiu lingva malneŭtraleco. La britoj havis grandegan avantaĝon: ili sinesprimis ege pli flue ol la ceteraj partoprenintoj kaj tio donis al ili pli altan statuson.

Kaj mi ne havas klarigon por la jeno: la konferenco atrofiigis niajn denaskajn lingvojn. Multaj portugaloj uzis anglajn vortojn en siaj paroladoj, pli ofte ol kutime. Se mi bone memoras, tio tute ne okazis al mi post IJK.

Nu, tre interesa konferenco ĝenerale. Konis multajn interesajn homojn kaj verŝajne partoprenos denove venontjare en Kroatio.

The features of Common Lisp

2008-08-20T14:30:00.005+01:00

Abhishek Reddy has compiled an interesting list of Common Lisp features. It's quite concise and includes examples for almost every feature described. It'll come in handy next time someone asks you what is it that attracts you to Lisp.

CFFI 0.10.0 released!

2008-07-29T23:24:00.006+01:00

It's been a while since CFFI's previous release, almost two years. During this period, a lot of development work happened and lots of cool new features were implemented. Here's a brief highlight of some of the important changes:

foreign string encodings using Babel. UTF-8 becomes the default encoding for foreign strings.
improved foreign type system that takes better advantage of CLOS features.
emulated :long-long types on Lisps whose native FFI doesn't support these types.
integrated a groveller inspired by SBCL's sb-grovel.
support for the stdcall calling convention.
removed finalizer-related code in favour of trivial-garbage.
function and variable lookups can now be linked to a specific foreign library instead of assuming a global namespace.
the cffi-features package has been deprecated in favour of trivial-features. CFFI-specific features are now interned in the CFFI-SYS package.
dozens of bug fixes and minor enhancements.

The long hiatus between releases caused all sorts of problems and confusions. Hopefully that won't happen again and you'll see more frequent CFFI releases in the future.

Paneo E-planeda

2008-05-23T09:55:00.004+01:00

Pro fuŝo mia, E-planedo estis neatingebla ĉi-nokte. Dankon al Kalle Kniivilä pro la atentigo. Ĉio enordas denove, mi esperas.

Mensagem dos Amigos da Cultura

2008-01-27T14:04:00.001Z

«Um grupo de pessoas de Coimbra resolveu juntar-se para manifestar o seu descontentamento com o rumo da política cultural em Coimbra, tendo daí surgido o texto “Pelo direito à cultura e pelo dever de cultura!”.

A sua apresentação pública e dos nomes dos 160 subscritores iniciais foi feita em conferência de imprensa no Café-Teatro do Teatro Académico de Gil Vicente, na quarta-feira passada. Em resultado, foi criado um blogue que está disponível para acolher novos subscritores e para publicar os depoimentos pessoais de todos quantos queiram enriquecer a discussão pública agora iniciada.

Foi igualmente anunciada a data do debate com o qual se pretende dar seguimento a esta iniciativa. Terá lugar no próximo dia 20 de Fevereiro, a partir das 17:00h, no Teatro Académico de Gil Vicente. A sua participação é essencial. Se tal como nós, entende que é urgente voltar a tomar posição pública sobre esta matéria que a todos/as nós diz respeito, visite o blogue e assine.»

originalmente publicado no blogue do Sítio de Sons

Podcasts sobre música e músicos

2008-01-01T21:32:00.000Z

Certamente muitos já conhecem o programa de rádio «Pessoal e... Transmissível» da TSF, que está também disponível em formato de podcast, mas que infelizmente não contém o nome dos entrevistados ou qualquer outra informação acerca dos conteúdos dos programas. O arquivo, por outro lado, embora tenha uma descrição de cada programa, não tem os ficheiros num formato que possa ser ouvido num iPod, por exemplo.

Digo isto porque neste programa de Carlos Vaz Marques houve já imensas entrevistas com excelentes músicos portugueses e estrangeiros que merecem ser republicadas e ouvidas com atenção. Seguem-se então as ligações para os ficheiros MP3 de algumas destas excelentes entrevistas: Maria João, Mário Laginha, Gary Burton, Carlos Bica, Hermeto Pascoal, Afonso Pais, Sofia Ribeiro, Egberto Gismonti, Zé Eduardo e Pat Metheny.

A entrevista com o Hermeto Pascoal é particularmente fascinante.

(originalmente publicado no blogue do Sítio de Sons)

E-planedo legebla per retpoŝto

2008-01-01T17:13:00.000Z

Ekde nun, eblas legi e-planedon per retpoŝto, se vi tion preferas. Se vi aliĝos, vi ricevos retpoŝtajn mesaĝojn po maksimume unu ĉiutage kun ĉiuj afiŝoj de la koncerna tago.

Dolĉa Rizo, Koimbro-stila recepto

2007-12-31T00:20:00.002Z

Kiel promesite, jen la recepto por prepari Dolĉan Rizon.

Ingrediencoj

por 6 personoj

250 g da rizo
1.5 l da lakto
100 g da sukero
citronŝelo
pulvora cinamo

Preparado

Boligu la lakton kun la citronŝelo.
Dume, varmigu 2 dl-ojn da akvo en poto. Kiam ĝi boliĝas, aldonu la rizon.
Post bolkuiri ĝin dum 3 aŭ 4 minutoj ekaldonu la lakton. Dum oni malrapide aldonadas la lakton, nepras ĉiam kirli (malrapide, per lignkulero). Tio daŭros pli ol unu horo.
Iam aldonu la sukeron. Atentu, tiam la rizo ne plu bolkuiriĝos, kaj bona rezulto estos rizo nek tro mola nek tro malmola.
Daŭre bolkuiru la miksaĵon. Ĝi iĝos pli kaj pli densa. Denove, tio estas arto; ĝi estu nek tro flua nek tro densa. Vi devas ĉiam kirli aŭ ĝi gluiĝos al la poto. Uzu malfortan fajron. Postulas multe da pacienco tiu ĉi dolĉaĵo.
Finfine surŝutu ĝin sur telerojn kaj aldonu la cinamon.

Frandumado

Manĝu ĝin tuj varman, manĝu ĝin poste malvarman, manĝu ĝin eĉ post unu aŭ du tagoj. Tiu ĉi dolĉaĵo, kiam bone preparita, bongustas ĉiam kaj ĉiel.

Dolĉa Rizo

2007-12-26T13:30:00.000Z

Iam mi scipovos kuiri! Dume, mi faras provojn. Jen la unua fojo, ke mi faras la tradician dolĉaĵon “Dolĉa Rizo”. (Internacie konata kiel “Rizpudingo”, mi kredas.) Ĝi tradicias ĉe mia regiono verŝajne pro la rivero Mondego kaj siaj rizkampoj.

Ĉifoje, mankis iom da rizo — mia patrino informas min, ke la recepto kiun mi uzis malĝustas kaj mi devintus uzi trifoje pli da rizo — kaj, kompreneble, ĝi ne estis tiel bongusta kiel tiu de mia patrino aŭ mia avino. Tiu ĉi dolĉaĵo postulas multe da pacienco kaj iom da sperto. Paciencon mi havis, antaŭsperton tute ne. Venontfoje, se la kuirado estos pli sukcesa, mi skribos pri la recepto. Tamen, sciu jam, ke tiu ĉi Koimbro-stila versio ne enhavas ovojn; tiujn kun ovoj mi tute ne ŝatas. :-)

Guglo sugestas studi Esperanton

2007-10-29T22:42:00.000Z

En sia ĉefa blogo, Guglo priskribas la spam-sistemon de sia retpoŝtservo, Gmail. Tiu blogero inkluzivas amuzan videon pri la sistemo. Per la tempo kiun oni ne plu malŝparas forviŝante spamojn, ili sugestas danci kaj... studi Esperanton!

Practical Common Lisp

2007-09-23T18:00:00.000+01:00

Just recently, I have finally bought Peter Seibel's book Practical Common Lisp.

I had already read most of it on the web. The chapters on CLOS and LOOP were particularly useful for me since the previous Lisp book I had read, Paul Graham's ANSI Common Lisp, largely neglects these important features.

What can I say? It's a great common lisp tutorial.

Update: as someone kindly mentioned in the comments, Seibel's book has a chapter dealing with CL's condition system, aptly named “Beyond Exception Handling: Conditions and Restarts”. This very important feature is also neglected by pretty much every other book about Lisp.

Dia do Blogue / BlogTago / BlogDay

2007-08-31T16:07:00.000+01:00

[pt] Esta entrada trilingue comemora o 3.º Dia do Blogue divulgando alguns dos meus blogues preferidos.

[eo] Per la jena trilingva blogaĵo mi celebras la 3-an BlogTagon diskonigante kelkajn blogojn kiuj plej plaĉas al mi.

[en] This trilingual post celebrates the 3rd BlogDay by promoting some of my favourite blogs.

Que Treta! (pt)

[pt] Este blogue português da autoria de Ludwig Krippahl é impecável. Trata temas que vão da biologia à política passando pela religião e a ciência. Faz pensar, e o cérebro agradece. É a minha recomendação #1.

[eo] Tiun ĉi blogon verkas portugale Ludwig Krippahl, kaj ĝi bonegas. Ĝi pritraktas temojn kiel biologio, politiko kaj religio. Pensigas, kaj la cerbo dankas. Mia rekomendo #1.

[en] This portuguese blog by Ludwig Krippahl is most excellent. It approaches subjects ranging from biology and science to politics and religion. Lots of food for thought here. My #1 recommendation.

E-planedo (eo)

[pt] Aqui são agregados vários blogues espalhados um pouco por todo o mundo, cujos autores escrevem em esperanto, uma língua auxiliar internacional.

[eo] Vi certe jam konas E-planedon. :-)

[en] This page aggregates various blogs spread all over the world, whose authors write in Esperanto, an international auxiliary language.

Planet Lisp (en)

[pt] Outro agregador de blogues. O tema deste é a minha linguagem de programação preferida, o Common Lisp.

[eo] Alia blogaro. Ties temo esta la programlinvgo kiun mi plej ŝatas, Common Lisp.

[en] Another blog aggregator. This one's about Common Lisp, my favourite programming language.

Schneier on Security (en)

[pt] A segurança, nomeadamente no que diz respeito ao terrorismo, é um tópico quente nos dias que correm. Schneier sabe do que fala e não tem papas na língua para criticar as más práticas de segurança, mentiras, mitos, etc.

[eo] Sekureco, nome rilate al terorismo, estas grava temo hodiaŭe. Schneier spertas pri tiu temo kaj ne hezitas kritiki malbonajn sekurec-praktikojn, mensogojn, mitojn, ktp.

[en] Security, namely terrorism-related issues, is a hot topic these days. Schneier is a security expert who doesn't hesitate to criticize bad security practices, lies, myths, etc.

TED Blog (en)

[pt] TED significa tecnologia, entertenimento e design. São esses os temas desta conferência anual onde participam pessoas como James Watson, Richard Dawkins ou Bill Cliton só para mencionar alguns nomes proeminentes. Entre outras coisas, neste blogue são divulgados regularmente vídeos com apresentações extremamente interessantes de conferências passadas.

[eo] TED signifas teknologion, amuziĝon kaj dezejnon. Pri tio temas tiu ĉi ĉiujara konferenco kiun partoprenas homoj kiel James Watson, Richard Dawkins aŭ Bill Cliton nur menciante kelkajn elstarajn nomojn. Interalie, tiu ĉi blogo ofte disponigas videojn kun ege interesaj prezentoj de pasintaj konferencoj. TED ja ne tedas.

[en] TED stands for technology, entertainment, and design. Those are the subjects of this yearly conference that features participations from people like James Watson, Richard Dawkins or Bill Clinton just to mention a few prominent names. Among other things, this blog regularly makes available extremely interesting video presentations from past conferences.

[pt] Dado que não participei nas duas edições anteriores deste evento, aqui ficam mais dez blogues que me agradam:

[eo] Pro tio ke mi ne partoprenis la du antaŭajn eldonojn de tiu ĉi evento, jen pliaj dek blogoj kiujn mi ŝatas:

[en] Since I didn't participate in the previous two editions of this event, here are ten more blogs I like:

trivial-features 0.1

2007-08-28T23:42:00.000+01:00

Google's Summer of Code 2007 is over so, over the next few weeks I'll be releasing the various stuff I worked on this summer.

First up is trivial-features which ensures consistent *FEATURES* across multiple Common Lisp implementations. Well, it tries to; patches for exotic Lisps, operating systems, and CPUs are welcome. Comments and suggestions are welcome too. Consult its cliki page for more details.

While we're on the subject of features, “Maintaining Portable Lisp Programs” is an interesting paper by Christophe Rhodes that discusses common pitfalls when using read-time feature conditionals and suggests some good practices.

My blog got comments

2007-08-06T02:22:00.000+01:00

Whoo hoo! My last few posts got some interesting comments, one of which mentions darcsum.el which is a nice Darcs mode for Emacs. My first impression with M-x darcsum-whatsnew is that it's not as nice as git-citool in one important way: it doesn't let me easily write my changelog while simultaneously picking what changes should be recorded. But it has some advantages too: its convenient keyboard shortcuts don't make me have to reach for the mouse and, hey, it's an Emacs mode. Still, no gitk-like repository browsing functionality.

Apparently, I'm not a Star Wars geek since I completely missed the “elegant weapons” reference in that xkcd comic about Lisp. Some people were upset about that.

Finally, it appears that dots in package or system names are generally disliked though it seems that's not something most people feel very strongly about. I don't like them.

Quick opinion poll regarding style

2007-08-04T05:30:00.000+01:00

Do you like dots in package or ASDF system names?

I do like them. (Please explain why.)
I hate them. They break the pleasant symmetries formed by parentheses, dashes, and colons. E.g., (foo-bar-quux:frob-baz-now) vs. (foo.bar-quux:frob-baz-now)
I don't care.

Please leave your answer in the comment form. Thank you.

Lisp featured in xkcd, again

2007-08-01T05:43:00.000+01:00

xkcd has mentioned Lisp before, but smug Lisp weenies will probably find this one funnier. As a bonus for Lispers who like to waste time playing Nethack — and there are quite a few, myself included — this comic includes a funny reference to the game, hah.

All the cool kids are using Git

2007-07-31T16:07:00.000+01:00

Yes, it used to be true that all the the cool kids were using darcs. Darcs is so 2005, though, so I've decided to take Git for a spin. Here's what I'm enjoying the most so far:

git-citool is a very cool GUI for picking what changes you want to commit, write the commit message, commit, push to a remote repository, and more. I love this little application. It lets me go through my changes in any order, go back to Emacs and fix any mistakes without losing my commit message or the list of changes I've already marked for commit. Love it.
gitk lets me visualize the repository history. All the patches, all the branches, all the diffs, all the commit logs, easily accessible within a few clicks. It's quite fast too.
Another useful feature git-citool has is a history browser that lets me browse my repository and see each file's history, which patches change which lines, navigate through the various past states of a file, etc.

And, of course, Git has all those great characteristics of a distributed VCS. I've missed some things from Darcs though:

For smaller changes I prefer darcs record over having to reach for the mouse with git-citool and git-add -i isn't as nice.
darcs revert allows me to revert individual hunks within a file, with a nice interface too.
darcs unpull and darcs unrecord allow me to get rid of patches without having to generate a reversion patch (which is what Git does if the patch you want to revert is not the very latest patch). Also, they keep any local changes untouched.
darcs pull lets me pull only the patches I want from another repository. I haven't found a way to do that in Git.
Darcs's no effort spontaneous branches are a joy. No need for explicit branch creation. You just create copies of your trees and move individual patches around whenever you feel like doing so. This way you can easily, say, merge only some of the changes from one branch into another, quickly discard a branch, etc.

Darcs has well-known performance issues, I've watched it sit forever trying to apply some patch. This hasn't been a great problem for me with the small projects I usually work on though, so I don't really regard that as a bit advantage of Git's.

For me, it's the tools. I have moved some of my stuff over to Git but I still like a lot of aspects of Darcs's workflow. Perhaps some more experience with Git will change my mind, or perhaps Darcs-Git will be the VCS really cool kids will be using in the future. We'll see.

If you're interested in trying Git out, have a look at Git For SBCL Hackers and Everyday GIT With 20 Commands Or So.

#lisp tip of the day

2007-07-25T17:40:00.000+01:00

Ever recompiled a function hoping to fix some bug only to find out nothing changed? Perhaps you passed #'some-function around and your live code is still dealing with the old definition? How to tell? Here's an example with SBCL:

* (values (symbol-function (defun foo ()))
          (symbol-function (defun foo ())))
STYLE-WARNING: redefining FOO in DEFUN

#<FUNCTION FOO {11E47CDD}>
#<FUNCTION FOO>

The old version is printed with its object identity (#x11e47cdd in this example), whereas the current global definition is printed without it allowing you to quickly tell which is which. This behaviour is not standard but, for example, OpenMCL provides similar information:

? (values (symbol-function (defun foo ()))
          (symbol-function (defun foo ())))
#<Compiled-function FOO (Non-Global)  #x85AE40E>
#<Compiled-function FOO #x85ADB06>

Your favourite Lisp might also do something along these lines. Great tip by Xof.

On UTF-16 vs. UTF-32

2007-04-24T04:17:00.000+01:00

It'd be more space-efficient [to use UTF-16] in most cases, and less time-efficient in all cases (either "somewhat so" or "grossly so".) Using UTF-16 internally is probably not nearly as far down the Bad Idea scale as... oh, Huffman-coded arrays would be. ("Newly created arrays are full of 0s! Why waste 31 or 63 extra bits? Of course, this makes (SETF AREF) hard, but you could have a bit somewhere!")

Gary Byers in openmcl-devel, discussing (here and here) why variable-length encodings are a bad idea for the internal representation of Lisp strings. An enlightening read, as usual.

Gugla Kodsomero 2007

2007-04-12T05:50:00.000+01:00

Mi ĝojas pro tio, ke mi estis akceptita de Guglo por partopreni ties programon Kodsomero 2007. Tio estas programo kies celo estas doni eblon al studentoj labori en liber-programaraj projektoj ricevante iom da mono dum la (nord-hemisfera) somero.

Mi jam partoprenis antaŭe, en 2005, kaj estis bonege. Ĉi tiu blogero, en la angla, havas pliajn detalojn pri mia ĉi-jara projekto. Ĉu partoprenos ankaŭ aliaj esperantistoj?

Sweet Summer of Lisp

2007-04-12T00:11:00.000+01:00

Yay! I have been accepted into Google's Summer of Code 2007 thanks to LispNYC. The project I will be working on is IOLib and you can check out my proposal. Any suggestions you may have for this project are welcome!

If I had to pick the single most important event during my participation in the 2005 edition, it would have to be when Christophe Rhodes suggested I should have a look at James Bielman's then recent project CFFI. Hadn't he done that, I wouldn't have had the great pleasure of getting to know James, working with him, learning from his code, etc... So, please, send those great suggestions to luismbo at gmail dot com!

I had sent another proposal, “Metaobject Sealing for CLOS”, which was a very cool idea suggested by Christophe (again) and I was actually expecting that one would be picked instead. I already had some code and was avidly reading the AMOP, not to mention that I even printed out SBCL's PCL source code. Oh well. If nobody picks that idea up, I would love to work on that after the summer. <blink>Perhaps ITA or Clozure could fund that.</blink>

You can see the list of accepted Lisp projects here.

One last thought. While I realize that it's not easy for Google to work around this, I find it pretty sad that students from Iran, Syria, Cuba, Sudan, North Korea or Burma aren't allowed to participate in this program. I sure hate politics.

XCL

2007-04-07T15:01:00.000+01:00

Peter Graves, of ABCL fame, has been working on this new Common Lisp compiler for a while now. Here's how he describes it:

XCL is a new, native-code CL implementation that features a kernel written in a very restricted subset of C++ and an optimizing compiler, written in Lisp, with backends for x86 and x86-64. It runs on Linux and Windows [...]

XCL supports threads on both Linux and Windows, and in principle the compiler is re-entrant.

Recently, and this is the actual news, Peter made available a link to a source code snapshot in #lisp. I couldn't resist trying it out, so here are some superficial first impressions:

It has an interpreter written in C++ and it uses that to bootstrap itself. This is similar to what ABCL does, though it seems that, at this point, it doesn't actually compile (all of?) its own Lisp code. Also, Peter says he's working on getting it to bootstrap SBCL.
Friendly REPL similar to Allegro's.

It features a neat, readable disassembler.

CL-USER(10): (disassemble (compile (defun inc (x) (1+ x))))
; Compiling INC
; Disassembly of #<FUNCTION INC {F84820}>
; Constants:
  NIL
; Code:
  E1BF50: 55                 push    %rbp
  E1BF51: 48 89 E5           mov     %rsp,%rbp
  E1BF54: 57                 push    %rdi
  E1BF55: 48 83 EC 08        sub     $0x8,%rsp
  E1BF59: 48 89 F8           mov     %rdi,%rax
  E1BF5C: 48 89 C7           mov     %rax,%rdi
  E1BF5F: A8 03              test    $0x3,%al
  E1BF61: 75 08              jne     L0
  E1BF63: 48 83 C0 04        add     $0x4,%rax
  E1BF67: 70 02              jo      L0
  E1BF69: C9                 leave
  E1BF6A: C3                 retq
L0:
  E1BF6B: BE 04 00 00 00     mov     $0x4,%esi
  E1BF70: E8 AB 47 60 FF     callq   0x420720   ; SYSTEM:TWO-ARG-+
  E1BF75: C9                 leave
  E1BF76: C3                 retq
; 39 bytes
NIL

Similarly to CLISP, its fasls are readable S-exps and pretty short too. They even start with -*- Mode: Lisp -*-, heh. The actual assembly code looks something like this:

(COMPILER::GENERATE-CODE-VECTOR
 '((:BYTE 1 85)
   (:BYTES 3 (72 137 229))
   ...
   (:JMP-SHORT 2 (:NZ #$G7248))
   ...
   (:EXIT 2 (201 195))
   (:LABEL 0 (#$G7248))
   (:BYTE 1 190) ...)

It managed to load ASDF—though not yet compile it—and use that to load and compile a simple system such as split-sequence. Given that (lisp-implementation-version) returns "0.0.0", and comparing to some other lisps that crash so easily with ASDF, I find this very impressive.

Incidentally, this is my first post to Planet Lisp. Hello world! I'm sure I've screwed it up in some way or another. In case you're wondering, the rest of my blog is in Esperanto.