freenode/#lisp - IRC Chatlog
Search
0:24:39
jason_m
I am working on a system and had a compile time error in one of my source files. When I quickload (asdf load) the system, I land in the debugger with a condition of type UIOP/LISP-BUILD:COMPILE-FILE-ERROR.
0:24:41
jason_m
I know I can look at the error in the inspector, but I don't see the actual underlying compile error.
0:27:55
jason_m
If I compile and load the particular file, I get a SB-INT:COMPILED-PROGRAM-ERROR which better directs me to the problem, but to get it, I abort from the debugger, open the file, and load that (or sometimes C-c C-c form by form) to get the more specific message.
3:23:34
beach
Showing specbot replies publicly is useful mostly to tell other people where to look, or to ask people for help on an entry.
4:41:24
oleo
(defun push-in (list) (let ((result))(dolist (x list (nreverse result)) (cond (t (push (list x) result))))))
6:15:39
flip214
jasom: don't you see the error message in the REPL output, along with the QL output?
8:30:04
akr
Hello, I'm printing out an argument to my function to figure out what it is, and all I'm getting is "[object Object]"
8:58:33
jdz
akr: no, I mean something that a JavaScript implementation (e.g., browser) would write to the console when an object is converted to a string instead of writing the object itself.
9:01:35
jdz
akr: also, instead of printing the value, you can use BREAK, and the inspector to inspect it.
10:19:54
jack_rabbit
If I declaim it in my repl, will that apply to packages I load with quicklisp and asdf?
10:24:58
jack_rabbit
It would be nice for a user to be able to specify that, so the library writer doesn't have to.
10:38:55
antoszka
Guys, would you be able to point me towards Peter Norvig's note about his PAIP book being not anymore very useful for AI but still considered a very good CL book?
11:09:19
malgrand
hey this is my first time using irc and this just seemed to ask lisp related questions. I was looking to learn a new language and make a text-adventure for fun in that language. Do you guys think that would be a good idea in lisp?
11:11:53
edgar-rft
malgrand, there's a book for learning lisp with lots of games: <http://landoflisp.com/>
11:25:19
lukego
Hey I'm looking at USOCKETS and wondering whether people have already been running this with lots of sockets and e.g. adopting the more hardcore platform-specific select()-like system calls. Anybody been up to such mischief already?
11:26:56
lukego
I'm actually hacking Lisp on a fun project. Story for another time :). But it's jolly pleasant.
11:29:26
lukego
I'm peeking in the USOCKETS code (do we still capitalize symbol names like that? :-)) and I see that on LispWorks Linux it's delegating to a builtin mechanism (MP:NOTICE-FD, MP:UNNOTICE-FD), and on LispWorks Windows it's doing scary Win32 API calls, and on CCL it's calling select() via FFI. Seems quite nice that there is a backend for each platform that provides an easy point to hack. Just vaguely wondering if there are git branches aro
11:36:18
lukego
I've looked briefly at lev. Seems like USOCKET would be the simplest integration point for that? Since you can already access things like file descriptors there to bridge the domain between streams and system calls.
11:38:47
jdz
But everybody was happy to see the Woo performance graph (https://github.com/fukamachi/woo) at ELS 2014.
11:42:39
jdz
lukego: This confirms it: https://github.com/fukamachi/woo/blob/master/src/ev/socket.lisp
11:44:32
lukego
That doesn't suit me because I want something portable. So the best option so far sounds like starting with usocket and hacking one or more backends to use libev.