libera/#clasp - IRC Chatlog
Search
11:59:56
Colleen
yitzi: drmeister said 7 hours, 57 minutes ago: I'm getting "Symbol named "ON-REMOVE" not found in the NGL package." How do I fix that?
11:59:56
Colleen
yitzi: drmeister said 7 hours, 14 minutes ago: I did this: rm -rf build dependencies src/lisp/kernel/contrib
11:59:56
Colleen
yitzi: drmeister said 7 hours, 8 minutes ago: Could ./koga --clean do rm -rf build dependencies src/lisp/kernel/contrib
12:26:19
yitzi
I've add a `--deep-clean`option to koga. It will delete an existing clone in repos.sexp before cloning. It respects `--skip-sync` and implies `--clean`
12:27:02
yitzi
So `--clean` deletes the build folder. `--deep-clean` deletes the build folder and gets fresh clones of the dependencies.
12:28:23
yitzi
Be careful if you keep a cando clone in extensions that you don't want koga to sync or delete. In that case you should put `:skip-sync '(:cando)` in config.sexp
12:29:39
yitzi
drmeister: No reason. Just the name that occurred to me. I think distclean is kinda weird, IMHO.
12:59:56
drmeister
I ran quickclasp update a couple of times last night. Does it need one this morning?
13:00:36
drmeister
The on-remove problem was only solved after I removed the contents of those directories.
13:03:32
drmeister
I searched for ngl-flu and removed all directories that contained that name. When I built it restored the old version of ngl-clj
13:04:27
drmeister
It was super frustrating because it failed at the very end of the build and I was building over and over again.
13:06:17
drmeister
I even wiped out ngl-cli in my quicklisp and quickload’d ngl-clj and that pulled the latest ngl-clj
13:12:44
yitzi
If CLASP_QUICKLISP_DIRECTORY is not defined then koga will clone quicklisp and maintain a copy in dependencies/quicklisp. This is intended for a packaging system when you don't want to use the "user's" quicklisp installation.
13:13:16
yitzi
If CLASP_QUICKLISP_DIRECTORY is defined then koga will use that that for sclasp & jupyter compilation.
13:15:23
yitzi
Because the stuff in dependencies/quicklisp is a "live" quicklisp distribution. If you had wanted to update it you would have had to do `CLASP_QUICKLISP_DIRECTORY=dependencies/quicklisp/ ./build/boehmprecise/clasp --non-interactive --eval "(ql:update-all-dists)"`
13:31:06
drmeister
This is on zeus - I don't have CLASP_QUICKLISP_DIRECTORY set on there but I do have it set on my mac.
13:54:37
drmeister
::notify karlosz I implemented multiple entry points in cclasp for the simple cases that only involve required + optional arguments. If the function lambda list involves &rest or &key or anything else - then the fixed arity entry points jump to the general entry point. You could do the same couldn't you?
14:00:50
Bike
yitzi: i merged your characters request - the tests all passed but for the disassemble thing, except for one that went screwy in a way that i'm pretty sure is unrelated to your PR
14:03:41
drmeister
I'm going to merge the vm branch into main. It builds fine with cando and it fixes a nasty bug from initialization of the partial implementation of the VM
14:08:53
drmeister
I've merged vm into main on zeus. I'm building on zeus to make sure it's clean and then I'll push it. Otherwise I'll have to pull again and build again.
14:11:29
drmeister
This thing about compiled-function-p may need to be cleaned up a bit once the bytecode compiler is in place. We will need to decide if bytecode is compiled. If we decide it isn't, then we need to keep the forms around so that we can compile them - right?
14:15:43
yitzi
When you pull from main you'll need to remove dependencies/ansi-test before rerunning koga
14:16:19
yitzi
Or you can be brave and use `--deep-clean` .... see the log for notes about its usage
14:17:11
Bike
i think the question of compiling bytecode again is a little different from the question of whether compiled-function-p is true of bytecoded functions
14:24:27
drmeister
Then I'll push and we can start the nightly packaging and see if it fixes any problems.
15:24:31
yitzi
drmeister: I am looking at the internal coordinate stuff. Seems like it blows up for vectors on the negative x -axis. Also, can I make sure I understand the angle orientation? Phi is the angle in the yz plane starting at +y and winding towards +z. Theta is the angle from tge x axis with 0 at +x and pi/2 at -x?
15:28:41
drmeister
Does it? I put it on the x-axis. Huh - does z-matrix mean second atom on z-axis? I never thought of that.
15:29:45
yitzi
Yeah. It seems really wonky to me. Your method matches up with the usual spherical coordinates of theta in the xy plane and phi on the z-axis
15:30:17
drmeister
Maybe I'm wrong about that - but it's a convention and the ultimate orientation of the molecule doesn't matter.
15:30:25
yitzi
Putting the second atom on the z-axis scrambles the angles around as I describe. I'm pretty sure.
15:42:42
yitzi
I think it is just coming from trying to normalize the vectors. Instead of doing dot/cross products we invert the coordinate matrix instead, I think that will fix it.
16:52:10
yitzi
drmeister: Looks like we have got some missing defines. Getting https://plaster.tymoon.eu/view/3346#3346
17:03:57
Colleen
karlosz: drmeister said 3 hours, 9 minutes ago: I implemented multiple entry points in cclasp for the simple cases that only involve required + optional arguments. If the function lambda list involves &rest or &key or anything else - then the fixed arity entry points jump to the general entry point. You could do the same couldn't you?
17:05:28
karlosz
hm... the part im getting hung up on is somethng like &optional (x nil x-p). You make an entry point for 0 arguments and 1 arguments, but the 1-argument entry point still needs to set X-P to T, so its not as if the 0 argument entry point could just fall through to the 1 argument entry point
17:24:48
Bike
yitzi: where does koga/ninja put fasls now? i'd like to delete them so i can start rebuilding from bclasp. or is there some koga thing i can use
17:26:47
yitzi
I have a branch to simplify that down to lib/cclasp/ ... not sure if I should finish or wait for bytecode to land