freenode/#clasp - IRC Chatlog
Search
8:17:57
scymtym
drmeister: i think quicklisp has a "bundle" feature for preparing a set of libraries such that they can be loaded without quicklisp
9:10:04
Bike
drmeister: i'm pretty sure c2mop doesn't define its own validate-superclass on clasp- it just imports the symbol, so closer-mop:validate-superclass is just an alias to clos:validat-esuperclass. which is why i suggested a different problem.
9:10:04
Colleen
Bike: drmeister said 6 hours, 14 minutes ago: Tomorrow can you explain to me how closer-mop is supposed to work with the existing clos? clpython defines several closer-mop:validate-superclass but they won't be called by the clasp clos code.
9:10:04
Colleen
Bike: drmeister said 6 hours, 11 minutes ago: Also, I tried to remove quicklisp from the cando startup but it's needed to resolve dependencies for some of the systems. I also need quicklisp to build the systems the first time cando is run. Is there a way around this? If not - we have to keep loading quicklisp at startup.
9:10:04
Colleen
Bike: drmeister said 4 hours, 58 minutes ago: - I think I uncovered a subtle problem with clasp's generic function dispatch when building clpython.
12:50:41
selwyn
i get a segfault every time i try to load some. it doesn't make sense to me because bitcode is surely loaded into clasp all the time during the build process?
13:07:45
Bike
CST isn't building with dev because it doesn't compile the ast interpreter correctly. this is something i can understand and fix
13:14:36
Bike
might be nice to force generate-ast/cst-to-ast to do no inlining or compiler macroexpansion, but i'll worry about that later
13:34:16
drmeister
selwyn: clasp May be trying to run constructors on load. Where is the bitcode coming from?
13:36:52
drmeister
In the clasp-cxx-demo repo there is a macro that I add to make that c++ compile to bitcode that loads
14:40:13
selwyn
drmeister: i tried to load double-vector-cxx.bc from demo-clasp-cxx-interoperation. also i tried to load some generated bitcode from the build process build/boehm/fasl/cclasp-boehm-bitcode/generated/cl-wrappers.bc since i figured that must work
18:01:01
drmeister
I've added a facility to clasp extensions that lets them take over command line argument processing.
18:01:32
drmeister
This way I can copy iclasp-boehm to icando-boehm and ileap-boehm and they behave differently depending on their filename.
18:02:47
drmeister
The parser isn't complete - but it's simulating "leap" - the computational chemistry setup program I wrote 27 years ago.
18:05:10
drmeister
icando-boehm (and ccando-boehm) start up clasp and load all of the cando chemistry code but they drop you into a Common Lisp repl.
18:05:44
drmeister
ileap-boehm starts clasp, loads all of the cando chemistry code and then starts a leap repl.
18:06:06
drmeister
ileap-boehm handles command line arguments differently than clasp does - so it takes control at startup and sets things up for itself.
18:17:35
selwyn
why is cando a clasp extension? does it need to be built alongside clasp at clasp build time?
18:28:08
drmeister
selwyn: Long ago I decided to split clasp from the chemistry code. Clasp is an implementation of Common Lisp and Cando is the code that enhances clasp with lots of chemistry functionality.
18:28:35
drmeister
To build them together all you do is you clone cando into the clasp/extensions/cando and then you build as normal.
18:29:00
drmeister
There is no why to it really - it's a simplest solution to a difficult problem of merging to large code bases.
18:30:55
drmeister
I generalized the idea of an extension - other people could write extensions for clasp.
18:32:54
selwyn
i am wondering whether the extensions mechanism is right for me - i am interested not so much in writing c++ code but integrating large c++ libraries that are already there. doing the exposure at build time would be convenient