Search
1:28:15
drmeister
No - because our static initializer is in the list of static initializers. It's just that we picked up a bunch more from header files.
1:28:45
drmeister
Also, our static initializer is also broken with lots of calls to $0x0 on linux
1:28:55
drmeister
The runtime linking appears to be broken.
1:29:15
drmeister
I've put in a question to the llvm ORC JIT developer on discord.
1:29:28
drmeister
He usually gets back to me in a day or two.
1:29:37
drmeister
I don't understand why this worked before but not now.
1:29:56
drmeister
Esspecially when I disable setUseOrcMCJITReplacement setUseOrcMCJITReplacement
1:30:13
drmeister
My keyboard iss crap and reppeatsss keys like crazy.
1:30:23
drmeister
I've given up trying to clean it up.
1:30:24
paulapatience[m]
I hate when that happens
1:31:00
drmeister
I'll check with Lang to see what's going on with static constructorss.
2:23:43
drmeister
https://www.irccloud.com/pastebin/1d3AwRDz/
2:23:55
drmeister
I'm having a problem with recursion - I think I'm missing out.
2:24:14
Bike
well, your patch-object function doesn't do any recursion
2:25:07
drmeister
Right - so what kind of recursion does it need to do?
2:25:23
Bike
it needs to call fixup on value-old if found-p is false, as we discussed earlier
2:26:03
drmeister
Did we discuss that?
2:26:38
Bike
yeah, around one o clock
2:27:28
Bike
so what is passed to make-record-patcher in circle-subst now?
2:31:12
Bike
fixup is called for effect, so it just needs to call fixup on value-old before returning it
2:34:34
drmeister
https://www.irccloud.com/pastebin/jzRoNnHX/
2:34:50
Bike
no, fixup will return nil or something
2:34:51
drmeister
After I take out the format statements.
2:34:59
Bike
do (progn (fixup ...) value-old)) or so
2:35:16
drmeister
fixup isn't allowed to return anything?
2:35:27
Bike
more like it doesn't have to return anything meaningful.
2:36:06
drmeister
Ok, this for patch-object?
2:36:07
drmeister
https://www.irccloud.com/pastebin/tlq41n3T/
2:36:20
Bike
i think that will be better, yeah.
2:37:46
drmeister
That does the trick.
2:38:03
drmeister
Here's the code...
2:38:05
drmeister
https://www.irccloud.com/pastebin/rIPSTsGZ/
2:38:37
Bike
still think make-record-patcher should only get the closure, though
2:45:38
drmeister
The C++ code only needs the mapping and I can't create a closure from C++.
2:46:55
Bike
why does the C++ code need the mapping?
2:47:00
Bike
doesn't it just pass it as an argument to the function?
2:47:20
drmeister
circle-subst takes the mapping and the object.
2:47:52
Bike
you could just pass (lambda (object) (circle-subst object mapping)) to make-record-matcher
2:48:02
Bike
or whatever the argument order is, you know what i mean
2:48:25
Bike
i say this because this mapping mechanism could have uses outside of ## patching
2:51:46
drmeister
But do I create patching objects from C++.
2:52:13
drmeister
I'm checking if I do...
3:11:27
drmeister
Rebuilding everything now.
3:11:38
drmeister
I set it up to just use the closure.
3:53:33
beach
Good morning everyone!
6:29:30
kpoeck
pathnames now have double strings
6:29:35
kpoeck
Loading #P""/Users/karstenpoeck/lisp/compiler/clasp-karsten/build/boehm/fasl/aclasp-boehm-bitcode/src/lisp/kernel/lsp/defstruct.faso""
6:32:00
kpoeck
that will be consequence of the __repr__ change
6:33:25
kpoeck
yes string Pathname_O::__repr__() const { must change too
9:38:38
kpoeck
Fixed in https://github.com/clasp-developers/clasp/pull/966