Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Ben Hyde
@bhyde
blob
the new cl-bson requires let-over-lambda, so as a side effect I encountered the error shown above. that's on ccl; following quickload 'let-over-lambda with my ~/.cache/common-lisp cleared out, and quick lisp all uptodate. having kicked the tires a tiny little bit I can see that cl-bson's continous integration passed for ccl six days ago; so presumably I'm doing something stupid; though in that case I'm doing it on two machines. any random suggestions would be delightful.
the Phoeron
@thephoeron
This message was deleted
which version of CCL are you using?
Ben Hyde
@bhyde
"Version 1.10-dev-r16165-trunk (Darwinx8664)" and "Version 1.10-r16196 (Linuxx8664)"
is there a known issue with ccl's version though; presumalby there isn't anythingn in let-over-lambda that's particularly stressful for a mature implementation
I'm perfectly happy to go off run this to ground myself ... i was just hoping you'd say something like "Oh yeah, there is/was an issue .. try this ..." :)
the Phoeron
@thephoeron
alas not
there are known issues with v1.9 32-bit on Windows
with both let-over-lambda and cl-isaac
feel free to open an issue on the repo for this, though
Ben Hyde
@bhyde
tx, more l8r ... one hopes :)
Ben Hyde
@bhyde
Bit of time to look at this.... pandoriclet-get and set look wonky. the backquote comma usage in them isn't inside of a backquote. The #' is written #`, which may be a hint that some reader macro additions are in progress; but in which case it may mean that my kit doesn't have loaded something the package didn't require, etc. I'll open an issue.
the Phoeron
@thephoeron
Ben Hyde
@bhyde
saw that, but it sort of ruins the quick in the quicklisp experience :)
the Phoeron
@thephoeron
as in?