Arnold Noronha
Arnold Noronha
On Lispworks, the default trivial-backtrace output is super verbose, with all the variables displayed. Now this is fine for development, but on production this is is still logged to stdout...
In theory usocket+bordeaux-threads should work fine on Lispworks. I use both Lispworks and SBCL, and have some code which doesn't work under LW (basically: restarting the lisp process while keeping...
I work on [Screenshotbot](https://screenshotbot.io), which is a screenshotbot/snapshot testing service, which automates all of the recording workflow. I'm also the original author of https://github.com/facebook/screenshot-tests-for-android, and previously built something very similar...
Unfortunately, it appears that LW hasn't defined a :lispworks8+ feature as of now, so we'll have to do this again when Lispworks 9 comes out.
returns: `news & events` which is incorrect. Basically LSX shouldn't be escaping constant strings, only variables.
I just had a similar library I built that went out in the same quicklisp version. (in fact just below lsx in the quicklisp release notes). https://github.com/moderninterpreters/markup/ I'm wondering if...
.. As opposed to just looking at prefixes. Previously, If you had an existing defpackage like this: (defpakage :foo (:import-from :bar/car :find))) And you imported bar::position, you'll end up with...
Simple flock based file locking for CL repository at: https://github.com/tdrhq/file-lock
Simple stuff, just a little bit of added convenience.
I've been using this for a while now. LW7 requires an extra option to make sure slot values are not optimized when using MOP. The second fix is minor, I...