David Vázquez

I am just back from a few days of holidays and have seen how active JSCL is! It is really exciting.

This rising is due to abeaumont probably. I stopped working, but he came up with an idea I liked. It is, why don't integrate JSCL into Conkeror? We would end up with a Lisp programmable browser… that's a practical reason! We did some tests locally and it seemed to work, but now it is time for improving JSCL itself.

It is not the only platform where JSCL could run on. I plan to add support for Node JS. Indeed, it will let us use the REPL and tests in the terminal in addition to the browser, which is a much more convenient way to program.

In the meantime, I would like to improve the compiler a little bit.

Suggestion and patches are very welcome if you want to join us.

https://github.com/davazp/jscl

Hello everyone. I have been away some days from the computer, but I am back now! I have spent two weeks in New York visiting such a great city. I had the opportunity to attend to a LispNYC meetup and enjoy the great atmosphere there. I hope to come back soon.

I have also a new laptop. Finally, I have to say, as I inherited the last one from my brother and I have been using it for 6 years. Most of the time it was good enough but it is becoming very annoying. For example, I could not compile SBCL because it was restarted due to overheating..

I feel like doing things now so I wish I could tell you new adventures soon.

I like old systems which expose a good part of their internals, specially when they are so simple. I created this animation using ditaa to illustrate how execution is done in Forth:

Of course, it only makes sense if you already know Forth. But I guess you do not know many languages where such thing is possible.

I have learnt a new trick these days. Did you know that you can declare an argument as a special variable? Quoting Hyperspec:

Each required parameter is specified by a parameter variable var. var is bound as a lexical variable unless it is declared special.

It seems to work also for optional and keyword arguments, but Hyperspec does not mention it explicitly. For example, yo can do:

(defvar *variable*)
(defun foo () *variable*)
(defun foobar (&optional *variable*)
  (foo))