Fernando Borretti

Both the Python and Ruby MSSQL interface libraries use FreeTDS, so I'm guessing it's a fairly standard thing and most people who have ot use MSSQL won't complain about that...

I've been getting this error on every SBCL newer than 1.2 for every package that uses cl-syntax. Anyone have any idea what this is about?

Yep, version 0.9. The solution @Rudolph-Miller gave works perfectly, but just about every project uses `(cl-syntax:use-syntax :annot)` rather than `(annot:enable-annot-syntax)`.

I cloned the latest `named-readtables` and put it in my `local-projects`, then deleted all `fasl` files and tried again. Same error. As an experiment, I ran `git checkout d4d41e9` on...

Ok, I decided to stop building different SBCL's and instead try the different versions of `named-readtables`. To my surprise, switching the second-to-last commit fixed it. I made sure to run...

Whenever I install Quicklisp, I clone `named-readtables` and checkout the second-to-last commit. Otherwise, yes, it's still happening. I've been meaning to report the bug to melisgl but it might be...

Oh yes, the emitter is very low effort. We definitely need to have a way to emit things in the pretty human-readable style.

I believe I've run into this problem before. This is almost certainly a problem with the scalar regular expressions.

Ok, some feedback, putting this through cl-libyaml shows the single quotes are stripped: ``` lisp YAML-EXAMPLE> (defpackage yaml-example (:use :cl) (:import-from :libyaml.macros :with-parser :with-event) (:import-from :libyaml.event :event-type)) (in-package :yaml-example) (defun...

I guess it shouldn't be too hard to fix the emitter. Though I'm not sure how. Maybe quote every string?