freenode/#ecl - IRC Chatlog
Search
3:47:44
hdasch
Hello, all. I'm new. And I'm stuck. I have weblocks/reblocks sample program running with SBCL. I'm trying to run that with ECL 16.1.3, but having difficulty getting the dependencies loaded. Parenscript has me blocked. Having done a (require 'ecl-quicklisp) I can load the Parenscript dependencies. But whet I (ql:quickload :parenscript) I get "Internal error: in file special-operations.lisp, position 10409. It
3:47:44
hdasch
says, further, "at (defun return-result-of ...)", and "Cannot coerce string TAG: to a base string". The character following TAG looks like a Unicode glyph rather than a colon. Position 10408 in special-operators.lisp is "(defun return-result-of (tag form)". The character following "tag" is a space. quicklisp/version.txt is "2019-02-16" Any idea of what's gone wrong?
3:50:02
pjb
hdasch: oh, perhaps ecl-quicklisp is a CL system… (require is usually used in emacs lisp, but not in common lisp).
3:51:56
hdasch
Oh, I found that recommendation in an irc log from this channel. Should I be using quicklisp/setup.lisp instead?
3:52:32
pjb
hdasch: this is what I would do, (load #P"~/quicklisp/setup.lisp") ; this is what I actually have in my rc file.
3:53:27
hdasch
pjb: Cool. I think I had issues with that. But if it works, I'll give that a try again. Thanks.
3:55:35
hdasch
pjb: I typed rather than pasted. Here's a paste: "Cannot coerce string TAG₁ to a base-string". But I see no colon in the source. Let me give your suggestion a spin.
3:57:41
pjb
The code is not conforming, since base-string are expected to contain only the standard characters.
3:58:57
hdasch
pjb: Not sure why I thought I had an issue with quicklisp/setup.lisp. Quicklisp does work with your suggestion. But I end up with the same error. But I only see the glyph in the error message. I do not see it in the source fille.
3:59:56
pjb
perhaps the file has some encoding, and ecl reads it with a different encoding, and/or prints it with a different encoding on a terminal using a different encoding.
4:05:54
hdasch
pjb: Hmm. I don't see any coding issue with the file. But I'm not sure I would see a coding issue if it bit me on the face. I do see that the after "(in-package #:parenscript)", there's a "(in-readtable #:parenscript)" So a named readtable, perhaps?
4:07:14
pjb
No, readtables are independent of the encoding used. The encoding transforms the bytes from the file into character. The readtable transforms the character into lisp objects.
4:12:19
hdasch
pjb: Makes sense. As I said, I'm new at common lisp. Let me scan through the file for non-Latin-1 code points.
4:14:09
pjb
Perhaps having (setf ext:*default-external-format* '(:utf-8 :lf)) in ~/.eclrc would help?
4:22:26
hdasch
pjb: You nailed it. There is a tag₁ earlier in the file. ext:*default-external-format* didn't help. But finding the Unicode certainly did. Let me try a bit of surgery. Many thanks for your help.
5:59:51
jackdaniel
ecl-quicklisecl-quickp is a contrib module in ecl which downloads quicklisp via http and does setup