libera/#commonlisp - IRC Chatlog
Search
8:35:19
pjb
nij-: When the answer is "No", it means it's not trivial to do. You can always do it, with sufficient work. If you want to change the evaluation rules, you may do something like in cl-stepper. https://gitlab.com/com-informatimago/com-informatimago/-/tree/master/common-lisp/lisp
8:36:08
pjb
nij-: then instead of (defpackage "MY-PROGRAM" (:use "CL")) you'd write: (defpackage "MY-PROGRAM" (:use "MY-RULES-LISP"))
8:41:55
pjb
nij-: as mentionned, there's no standard way to change the evaluator (ie. EVAL, COMPILE and COMPILE-FILE). BUT you can either feed the evaluator some changed code like cl-stepper does, thru different macro expansions, OR you can use a different evaluator: write your own MY-RULE:EVAL, MY-RULE:COMPILE, MY-RULE:COMPILE-FILE, and the functions that call them such as MY-RULE:LOAD, and use them instead of CL:EVAL, … CL:LOAD.
8:42:53
pjb
nij-: note: this is a common occurence, for example, CLIM defines its own objects and methods. A clim application (:use "CLIM") instead of "CL", and you get clim:defmethod instead of cl:defmethod, etc.
9:04:03
pjb
Hmm, in McCLIM, there's both a CLIM-LISP and a CLIM package, that re-exports most of CLIM-LISP stuff.
11:01:59
jcowan
One issue with rewriting code (and this applies both to macros and to run-time rewrites) is that all's well when the input is fine, but a compile-time or run-time error will be given in terms of the transformed code rather than the original code. C and Scheme both have facilities to help with this.
11:10:53
dirtcastle
I want to get stumpwm running. it works but the modules don't work. stumpwm-ql in community package loads properly but I think it's not working as intended.
11:32:12
jackdaniel
the package CLIM exports CLIM symbols, CLIM-LISP is a drop-in replacement for the package COMMON-LISP
11:54:15
contrapunctus
dirtcastle: removing Arch's SBCL is an Arch package management question (which I'm not knowledgeable about). SBCL has binary releases on its website IIRC.