Show newer

Today I'm programming with the Cowboy Bebop soundtrack in the background. :-)

What should I work on in next?

Could you guess what this #lisp program does? (originally written by @luismbo)

(let ((lisp 'common-lisp))
(let ((fn (lambda () lisp)))
(let ((funcall (lambda (ignore) 'scheme)))
(let ((lisp 'elisp))
(funcall fn)))))

I've repackaged DejaVu fonts for Quicklisp - they are now available under the system named cl-dejavu[1]. That should be a good alternative to everchanging paths to system fonts (i.e as a sane default for ).


bottom-right picture presents a transformed ink (rotated in this case) - that uses a possibly hardware-accelerated function xlib:render-set-picture-transform.

Show thread

Success! I've got right the flipping ink over the xrender extension.

I'm rewriting 's CLX backend renderer to always use XRender extension. I've already drafted a core abstraction.

Fun fact #42: people seem to accept, that if you swing a radio onto the wall, it may stop working; otoh when they DDOS an innocent library from multiple threads with funcalls and it has race conditions they scream "a bug, a bug!"

You are right, but only if you take that the translated code is the product. In my case it is a by-product of thinking about code, such pseudocode is meant to reflect on my _understanding_ of the code, not the code itself.

To use a somewhat disconnected example - writing a text (say, for a blog post) makes you think about things you write about, without making mental shortcuts (which sometimes happen to be fatal flaws in the reasoning).

Re-reading what you wrote provides additional insight.

Sometimes to better understand a reviewed C code I'm rewriting it in Common Lisp pseudocode for clarity.

Show older

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!