Search
Thursday, 16th of November 2017, 14:15:53 UTC
14:54:56
drmeister
Argh - Is there a way to turn off *print-pretty* for trace?
14:58:52
drmeister
I presume that trace is binding *print-pretty* to T and the traces are unreadable because the lines are very, very long
15:01:29
Bike
also print pretty usually reduces line length since it inserts newlines in code.
15:02:52
Bike
(princ (with-output-to-string (*trace-output*) ...) *trace-output*) haha, what the fuck
16:37:09
_rumbler31
coffee not on board yet?
16:39:05
beach
_rumbler31: What do you mean?
16:40:04
_rumbler31
bike's post. his comment suggests the code doesn't make sense,
17:22:03
Bike
it redirects prints to *trace-output* into a string, and then prints that string to *trace-output*. so you could have the "..." by itself to get the same effect less convolutedly. unless i'm missing something.
18:18:02
Bike
it's onto compiling cleavir
18:19:15
drmeister
I'm gingerly crawling into the dark cave that is the Clang C++ AST. My goal is to recover template argument of a template type like: gctools::GCBitUnitArray_moveable<1,unsigned int,int>. There are snipes and wumpusses in here.
18:19:28
drmeister
I'm trying to avoid getting eaten.
18:41:44
_rumbler31
bike: thats what I thought too
18:48:19
drmeister
Got it - I should be able to define simple-bit-vectors and simple-signed-crumb-vectors(2bit) simple-unsigned-crumb-vectors (2bit unsigned), simple-signed-nibble-vectors and simple-unsigned-nibble-vectors now.
18:48:32
drmeister
I'm taking votes on what to name them.
18:54:10
drmeister
There are several names for 2 bit values on Wikipedia - I thought that was the most evocative.
18:54:35
eudoxia
I was literally looking that up lol
18:54:49
eudoxia
TIL the "shannon" is a standarized synonym for a bit
18:55:48
Shinmera
What are 2bit vectors useful for?
18:59:58
Bike
it got most of the way through inline, and in inline it tries to define a compiler macro on array-row-major-index
19:00:06
Bike
which is for some reason not in the list of symbols the interpreter defines
19:02:26
Bike
it does not seem to be in symbols_scraped_inc
19:19:56
Shinmera
beach: I suppose. I don't know if it'll be worth creating specific array types for though.
20:54:28
drmeister
Bike: Can you remind me why you can't macroexpand do-symbols and use that?
20:57:33
Bike
the macroexpansion refers to several support functions which are nontrivial
20:58:19
drmeister
And what is the problem that that causes?
20:58:29
drmeister
I'm just trying to cook up a solution.
20:58:35
Bike
i'd have to completely rewrite it in pidgin
20:59:01
drmeister
Oh - I speak pidgin Common Lisp.
20:59:11
drmeister
So a pidgin Common Lisp solution would be acceptable?
21:00:02
drmeister
I'm trying to stay away from a C++ solution that creates loads of new pointers that need to be fixed.
21:00:20
Bike
sure, i don't care what does it
21:00:26
Bike
it's just complicated, is all
21:00:48
Bike
do-symbols expands into a few loops with hash table iterators
21:09:30
drmeister
https://www.irccloud.com/pastebin/ewlw0TRK/
21:09:45
drmeister
ACTION speaks fluent pidgin Common Lisp
21:10:05
drmeister
If you want just the external symbols then leave out the maphash over the internal ones.
21:10:24
drmeister
Hang on - checking the order of values returned by (core:package-hash-tables ...)
21:10:40
drmeister
It's the other way around - hang on...
21:11:19
drmeister
https://www.irccloud.com/pastebin/mnGh11aJ/
21:11:23
drmeister
Would that work for you?
21:11:34
drmeister
That runs in iclasp-boehm -I -n
21:19:35
drmeister
No problem - I'm just glad not to have to do it in C++.
Friday, 17th of November 2017, 2:15:53 UTC