freenode/#clasp - IRC Chatlog
Search
11:20:04
kpoeck
rlwrap seems cool, I now do rlwrap -c -b "()\";" -i --file clasp-word-list build/clasp having dumped all external symbols of :cl :core & :ext in clasp-word-list
12:09:21
wuehlmaus
i have and honor emacs btw. it's just that my spacemacs and the slime REPL seeom to colide a bit that is why i wanted to use plain sbcl REPL
12:11:20
wuehlmaus
me [microemacs] was my second editor on Atari ST, then in 1994 i came to know and like emacs, so it's not that i have many problems with the old flame war, i love both emacs and vim :-)
12:12:52
wuehlmaus
first editor was ue which was the editor built into golem my first shell on ATARI ST,so tiny
12:19:37
wuehlmaus
oh, that's sad to hear. i am so used to using vim that i don't experience that emacs experience.
12:39:09
kpoeck
stassats: But is there any useful alternative for editing lisp code apart from emacs/slime? I learned common-lisp on MCL so I am still said about the loss of FRED
15:46:26
kpoeck
Triggers nearly immediately a compiler error with (test-random-integer-forms 4 2 200)
16:03:21
drmeister
Hi kopeck We will take a look tomorrow. I’m tied up today. But it’s good to find more broken test cases.
16:11:31
drmeister
::notify Bike I rethought stuff on the plane - we should implement the accessors using the MIR instruction memref2-instruction and memset2-instruction
16:12:47
drmeister
I'm adding constants for the offset of a field in bytes using a tagged pointer - then we just add a cleavir-hir-to-mir:specialize method on the instruction that uses the offset.
16:22:26
kpoeck
Best error message ever: ../../src/main/main.cc:260 There was an unhandled std::exception in process [pid: 59224] e.what()=[boost::too_many_args: format-string referred to fewer arguments than were passed] - do something about it.
16:23:16
kpoeck
fprintf(stderr, "%s:%d There was an unhandled std::exception in process [pid: %d] e.what()=[%s] - do something about it.\n", __FILE__, __LINE__, getpid(), e.what() );
16:28:58
frgo
kpoeck: You get the correct error message: "your" error is: that somewhere (not in the error message!!!) too many args where passed to bfornat() ...