Closed lukego closed 1 year ago
This looks good, but wouldn't it be even better if we had some kind of stable-read-from-string
in :slynk-backend
package that abstracted away this detail?
Yet another alternative would be to call FIND-SYMBOL
which does the job more directly. I did it that way at first but switched because the diff was harder to read/check and I didn't have access to all platforms to test.
Yet another alternative would be to call FIND-SYMBOL which does the job more directly. I did it that way at first but switched because the diff was harder to read/check and I didn't have access to all platforms to test.
Yes, and FIND-SYMBOL, like intern, doesn't seem to be read-table sensitive. But as I remember it, it's also not quite as practical (can't remember why). Anyway, I added another commit to this PR that simplifies this for anyone wanting to come along and do the right thing in slynk-backend.lisp
. Can you test it?
Add robustness to symbol lookups of the form:
by giving them stable reader settings:
so that they work the same independent of the reader settings in the image.
(I noticed that SLY compile commands stopped working when I was using named-readtables and :PRESERVE case. SLYNK would start looking for symbols with lowercase symbol-names.)