11:45:08Selwynclasp doesn't seem to recognise the #+ reader macro at times, i get an error "Undefined reader macro for char '#' subchar '+'" while loading a system
11:45:51Selwyni can work around it for now, can provide details for those interested. the confusing thing is that the #+ macro works fine when clasp subsequently drops into the debugger
11:47:20frgocracauer: I will be using FreeBSD in a few days ...
14:05:56Selwynthere is already a port of gsl to lisp called the GSLL which uses cffi. it works in clasp with some minor modifications mostly to the grovellers
15:20:11Selwynis clasp likely to complain about page faults?
15:25:48frgoSelwyn: What do you mean by "page faults"?
15:42:58Selwynin short, whatever SBCL means when it talks about page faults. when I run some diagnostics using GSL on SBCL with (time ...) , it often reports '98 page faults' or something like that. i am told that this is sometimes indicative of poor memory management. i wonder if clasp does the same. this is not a great concern at the moment though.
15:43:53kpoeck_regarding the readtable issue, my first bet would be in the form (named-readtables:in-readtable :antik)
15:44:52kpoeck_or better the cause might be https://github.com/clasp-developers/clasp/issues/391
15:46:33Selwynhttps://gitlab.common-lisp.net/ssimsek/gsll/tree/clasp-devel it's not pretty. it requires the clasp-compatible trivial-{features,garbage} libraries, and troublesome read macros have been purged from source code for the time being.