freenode/#lisp - IRC Chatlog
Search
12:18:37
Colleen
Unknown command. Possible matches: 8, set, say, mop, get, hello, grant, time, tell, roll,
12:19:25
Colleen
pjb: Unknown command. Possible matches: 8, tell, set, get, time, help, deny, say, mop, test url,
12:22:33
Colleen
runs: Unknown command. Possible matches: 8, weather, set, say, mop, get, notify, grant, block, award,
13:15:06
ebzzry
Is usocket *the* cross platform TCP/IP solution? I want to port a LispWorks library to use it.
13:18:47
White_Flame
it's quite high in use: http://blog.quicklisp.org/2018/03/download-stats-for-february-2018.html
13:43:52
White_Flame
ebzzry: looking at usocket's lispworks backend, it looks like they're all in the comm: package https://github.com/usocket/usocket/blob/master/backend/lispworks.lisp
14:20:39
drmeister
https://github.com/quicklisp/quicklisp-client/blob/master/dists/quicklisp/software/manifest-20120208-git/manifest.lisp#L274
14:26:02
phoe
the variable "symbol" is meant to be a symbol and therefore calling FIND-CLASS with a non-symbol invokes undefined behavior
14:26:34
phoe
I mean, the spec says that it may return an unicorn because the behavior is undefined in such a case
14:35:28
phoe
I see. Then it's manifest's fault for invoking UB in the first place if it calls FIND-CLASS on non-symbols.
14:40:05
phoe
the :IS form seems like a filtering predicate that checks whether a thing falls into a category
15:42:41
oleo
http://dpaste.com/22F1R3C http://dpaste.com/1QRCND6, i did a backtrace for the last one but have still no clue what's wrong
15:45:16
pjb
oleo: typing v on the line 0: in the backtrace should jump to the source line, and you should see where the library value comes from. It's probably the variable that's bad, according to the error message.
16:10:47
oleo
and #.(declaim (optimize (safety 3) (debug 3) (space 0) (speed 0) (compilation-speed 0) (inhibit-warnings 0))) is not good enough ?
16:57:20
oleo
but if i were to speculate, it either is some loop gone wrong, types not fitting or some conversion stuff in between.....
17:58:12
makomo
::notify Shinmera please take a look at the PR i've made for 3d-matrices. i think MLOOKAT is incorrect, hopefully i got it right (i've been at it for the whole day ;_;)
18:12:45
sjl
makomo: Shinmera generally hangs out in #shirakumo, not here, so if you want to get ahold of him it's best to try there
18:14:57
Colleen
makomo: Shinmera said 13 minutes, 36 seconds ago: Yeah as I mentioned in the reply, I've been at that for fucking ever before as well. If you really got it right now that's fantastic.
18:20:15
phoe
are you really chatting via Colleen now despite you guys being in two different channels
19:08:29
mfiano
Is there a way to reset the reader/printer control variables to the _default_? WITH-STANDARD-IO-SYNTAX seems to define it's own standard behavior, going against the defaults. For example, *print-readably* is defined to have an initial value of NIL, whereas WITH-STANDARD-IO-SYNTAX uses T
19:09:46
mfiano
phoe: I mean for things like *print-readably*, the standard defines it's initial-value to be NIL
19:12:16
phoe
You could try defining your own macro for that - I can't see it around from a very brief glance.
19:14:03
mfiano
Ok. I just spent a while debugging why i could not print CLOS objects, and *print-readably* was bound to T everywhere in a huge project. Turns out, I wrapped another library that calls this one in `with-standard-io-syntax`, in order to ensure things like floats being read correctly...i didn't realize *print-readably* is different than the defaults. I understand why it is though; it's really meant to make
19:22:33
mfiano
It seems the only one that differs from the defaults, aside possibly some implementation-specific ones, _is_ *print-readably*
22:13:24
jmercouris
is there a way to do (loop for item in list collect ...) and have the index of "item"?
22:28:28
pjb
phoe: no, that's the point, there is no "the" index of item! There are several indices of item!
22:28:57
pjb
(loop with list = '(1 2 1 2 3 4 1 2 3 4) for item in list collect (positions item list)) #| --> ((0 2 6) (1 3 7) (0 2 6) (1 3 7) (4 8) (5 9) (0 2 6) (1 3 7) (4 8) (5 9)) |#