Search
Monday, 21st of May 2018, 22:33:58 UTC
23:06:02
iqubic
Looks like quantum computer programmers are turning to lisp.
23:06:04
iqubic
https://www.youtube.com/watch?v=svmPz5oxMlI
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:24:50
jason_m
Can I get to that in the debugger/inspector?
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.
2:48:43
beach
Good morning everyone!
3:21:29
specbot
http://www.lispworks.com/reference/HyperSpec/Body/m_check_.htm
3:22:24
beach
vtomole: You can communicate with specbot like this: /msg specbot clhs check-type
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:37:29
vtomole
Is there a CL procedure that does "'(1 2 3 4) -> '((1) (2) (3) (4))"?
4:40:10
rme
you could use (mapcar 'list '(1 2 3 4))
4:41:24
oleo
(defun push-in (list) (let ((result))(dolist (x list (nreverse result)) (cond (t (push (list x) result))))))
4:56:39
johnvonneumann
** NICK Guest6374
6:15:39
flip214
jasom: don't you see the error message in the REPL output, along with the QL output?
7:20:21
DataLinkDroid4
** NICK DataLinkDroid
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:30:17
akr
how do I examine this further?
8:31:36
jackdaniel
sjl: are you aware of the collect macro from cmuutils?
8:33:00
jackdaniel
http://hellsgate.pl/files/9aafd32b (implementation curbed for my local utils)
8:54:29
jdz
akr: that looks like JavaScript.
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.
8:58:53
jdz
akr: this is #lisp, btw.
8:59:40
akr
jdz: well, it's what (format nil "~a" arg) literally returns
9:00:17
jdz
akr: what implementation?
9:01:35
jdz
akr: also, instead of printing the value, you can use BREAK, and the inspector to inspect it.
9:02:18
jdz
I still wonder which library has customised the printing to print objects like that...
9:02:35
akr
oh, cool, didn't know about break
9:02:43
akr
shrdlu68: thanks, that helps me a bit
9:03:50
shrdlu68
Very unhelpful print-object method.
9:04:58
akr
okay I see there is an issue on the frontend javascript, jdz was right all along
10:17:14
jack_rabbit
Is it good or practice to (declaim (optimize ...)) inside library packages?
10:19:15
loke
Well, it's acceptable as long as SAFETY isn't reduced
10:19:54
jack_rabbit
If I declaim it in my repl, will that apply to packages I load with quicklisp and asdf?
10:23:46
loke
jack_rabbit: Hmm.. I don't think so.
10:24:33
jack_rabbit
I didn't think so either.
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:26:31
loke
jack_rabbit: You can, but it's an implementation-specific extension
10:27:06
loke
For SBCL, look up SB-EXT:RESTRICT-COMPILER-POLICY
Tuesday, 22nd of May 2018, 10:33:58 UTC