freenode/#lisp - IRC Chatlog
Search
5:26:22
gjvc
I am using emacs and slime. (merge-pathnames "myfile-.xml" *compile-truename*) is returning something in /tmp not in my source directory
5:44:15
loke`
gjvc: I recommend you do create an ASD file and then load the project through Quicklisp
8:59:45
heisig
The ELS'18 recordings are finally available: https://29660.net/2018-04-european-lisp-symposium.html
9:13:48
aeth
"good morning" at 00:41 https://29660.net/els2018/sound/01%20-%201200%20-%20IncrementalParsing%20-%20RobertStrandh_mono.mp3
9:16:59
schweers
Cool, thanks for these heisig! Also obviously a big thanks to everyone who contributed to this.
12:37:59
daniel1302
Yes sorry I am reading your posts only and with irssi i just wants to switch windows, but sometimes it paste CRTL+C to the terminal. Its windows terminal error :(
12:58:24
dim
personnaly I still like using RCIRC within Emacs, some use ERC, and I think there's also a McCLIM application for IRC, it's all Common Lisp!
12:59:42
dim
jackdaniel: let's propose that for newcomers and have then hack their way around as a way to learn CL with a “real project”?
13:02:13
dim
franckly, it does not look that bad at https://common-lisp.net/project/beirc/images/beirc.png
13:03:13
jackdaniel
design is raw but acceptable, by ux I've meant things like connecting to a server and such
13:03:50
dim
well they seem to have /connect, but yeah, maybe storing some preferences and auto-connect would be good; sounds easy enough for newbies though?
13:06:30
dim
I spent too much time setting up rcirc, it felt like rewriting ERC at some point... I'm not ready to trash that investment...
13:10:41
jdz
https://bitbucket.org/jdzerins/dot-emacs.d/raw/91039016b61371c9c5171561607c834399ce7a19/site-lisp/setup-irc.el
13:34:54
dim
with 1.5.2 I had to declare the type as ((vector (unsigned-byte 8) 4) data), I first did simple-array and got the error you have
13:36:13
dim
WAIT, here's what I have when using ((simple-array (unsigned-byte 8) 4) data): Derived type of DATA is (VALUES (SIMPLE-ARRAY (UNSIGNED-BYTE 8) (* * * *)) &OPTIONAL), conflicting with its asserted type (VECTOR (UNSIGNED-BYTE 8) 4).
13:38:02
dim
https://travis-ci.org/dimitri/pgloader/jobs/531261798 --- that's a full compile of pgloader with a git clone of cl-db3, done with SBCL 1.5.2, and no complain
13:40:39
Xach
dim: does it build with ql:quickload or something? it does not look like it's using the critical :verbose t option as far as I can tell
13:48:00
Xach
dim: (simple-array (ub8) 4) is a four-dimensional array, (simple-array (ub8) (4)) is a vector of four elements.
13:49:55
dim
what about using a vector instead, so that I can then use svref? does it matter, and if yes, how to go about that?
13:51:26
scymtym
dim: if you are already using nibbles, you could use nibbles:[simple-]octet-vector. if i recall correctly, those do what you want in a less error-prone way
13:52:24
dim
it does not seem like simple-array declaration is compatible with then using svref, and I can of remember that svref can make things faster compared to aref, because it's specialized and doesn't have to deal with the many corner cases of a general array
13:52:28
jackdaniel
specialized vector is a vector with elements of known type (and implementaiton support)
13:53:36
Xach
a type-declared simple-array of unsigned-byte 8s will be better (on sbcl with its useful use of type declarations)
13:54:59
dim
scymtym: that's my whole patch, basically, repeated at several places, some of them being (8) rather than (4)
14:01:33
scymtym
out of curiosity, what was the problem with the original (vector (unsigned-byte 8) 4) declarations?
14:20:51
scymtym
Xach: the warning in the report you linked shows the rank 4 problem which the vector declaration shouldn't cause, so i'm not sure what the original problem was. but it's not important
14:21:02
scymtym
dim: https://github.com/dimitri/cl-db3/blob/master/db3.lisp#L288 should ensure that READ-SEQUENCE returns 11, otherwise NAME may only partially be populated from the stream