cl-dbi
cl-dbi copied to clipboard
Error in installing by Quicklisp with SBCL
when i tried to use it by sbcl, clone it on quicklisp/local-projects, register-local-projects and quickload it, then i got the error.
To load "dbi":
Load 1 ASDF system:
dbi
; Loading "dbi"
[package dbi.error]Unhandled EDITOR-HINTS.NAMED-READTABLES:READER-MACRO-CONFLICT in thread #<SB-THREAD:THREAD
"main thread" RUNNING
{1002BDD2A3}>:
Reader macro conflict while trying to merge the macro character #\# from
#<NAMED-READTABLE CL-ANNOT::SYNTAX {1005BDFDC3}> into
#<NAMED-READTABLE :CURRENT {1005D1C163}>.
though it caused with SBCL, it didnt cause with CLISP
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?
The method to avoid this problem is that adding :cl-annot to asd files, and (cl-syntax:use-syntax :annot)
-> (annot:enable-annot-syntax)
.
Though I use SBCL 1.2.1 usually, I don't have any problems so far.
named-readtables recently got a new maintainer and made some changes. https://github.com/melisgl/named-readtables
Do you guys have the latest named-readtables?
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)
.
Seriously?
I could reproduce the issue with the older named-readtables (at https://github.com/melisgl/named-readtables/commit/d4d41e97faba296a1f89b706b573a4cba8d1fbde).
Don't you have an old copy of it somewhere?
(asdf:system-source-directory :named-readtables)
might help.
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 the project, deleted all fasl
s and tried again. Same error.
EDIT: This is on SBCL 1.2.0, and on the latest SBCL. CCL works fine.
Weird. @m2ym may have some advices.
I don't have any idea but
Reader macro conflict while trying to merge the macro character #\# from
seems to say your macro character #
differs from the standard that is used by annot
syntax table. What do you get if you eval (get-macro-character #\#)
?
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 ql:register-local-projects
(Where my clone of named-readtables
is) and delete all FASL files from the system. I'll bring this to the maintainer of named-readtables
, but I think we can consider this issue closed on this end.
Is this still happening?
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 a little hard to prove, since it apparently only happens to a select few.