freenode/#lisp - IRC Chatlog
Search
19:44:38
thijso
My idea was to wrap the (wait-for-input ...) call in an unwind-protect, where the socket gets correctly closed in case of failure. Then the function that called udp-start-server in the restart calls that same function again, re-connecting the port. But I'm not sure if this is the correct way to do this.
19:45:20
Josh_2
if an error is called it just attempts to restart the function in a networking context
19:50:29
Josh_2
Plaster has absolute murdered the indentation, I think it is because I use tabs not spaces ¯\_(ツ)_/¯
19:52:13
thijso
jmercouris: yeah, that's next on my list to figure out, but I'm having trouble debugging as it's threaded code. I'm using the udp port to also send dump commands, so I can see what is going on. Bit of a hack, I know, but it works. As long as I have the UDP port to talk to...
19:52:51
Josh_2
thijso: you can print to standard output with a background thread by printing to *standard-out* if that helps with debugging
19:53:43
jmercouris
thijso: I guess my question is, if you are just listening on the UDP port, why does it crash? is it *what* you are doing with the data that you listen to that is causing your program to crash?
19:54:41
thijso
The issue I'm having is not printing to stdout while my program is behaving. The issue is that my errors seem to miss a lot of information when they happen. It's a lot less than what I get in slime, for example.
19:55:14
jmercouris
thijso: aha! well then, I should inform you about the two types of slime you can have
19:56:00
jmercouris
thijso: you can have a ~/.swank.lisp like this (setf swank:*communication-style* :spawn) or like this (setf swank:*communication-style* :fd-handler)
19:57:45
jmercouris
I'm not sure exactly, I believe FD handler is file descriptor handler rather than a BSD socket
20:00:00
thijso
Ah, yes. But I'm running the code without swank or slime, as I need to run x instances (nodes) that talk to each other.
21:13:13
eich
Hey everyone, I just downloaded CLisp from sourceforge. how can I build from source on a mac?
21:36:04
remexre
is there a builtin to turn a (vector unsigned-byte) to a bit-vector in big-endian order?
21:38:39
kpoeck
than ./configure --with-libiconv-prefix=<yourlibiconvpath> --with-libsigsegv-prefix=<yourlibsigsegvpath> --with-libreadline-prefix=<yourlibreadlinepath> --with-libffcall-prefix=<yourlibffcallpath> --cbcx <directoryname>
0:10:15
remexre
is there a way with iterate to iterate through all the active elements of an arbitrary array?
7:25:49
ljavorsk
Hi everyone, does the lisp libraries have any name template for package name? (something like: lisp-<name>)? I have this problem, I'm packaging the pgloader-bundle and in the bundle section in Packaging Guidelines is written that every bundled library within this package must be in 'Provide' section. I wanted to start with the alexandria library, but I've found that alexandria exists in fedora, but it's some ruby package and this
7:28:07
flip214
ljavorsk: Debian uses eg cl-alexandria - collection of portable Common Lisp utilities
7:29:22
jdz
It is my understanding that the whole "bundle" thing is so that pgloader does not interact with packages provided from other sources.
7:30:50
flip214
ljavorsk: how much value do you put on compatibility? You could have binary packages with only one FASL file, that would only need the exact matching SBCL version to work
7:33:02
jdz
ljavorsk: I bet it's so that the dependencies are in a known-good state (from the developer's point of view), and not some package maintainer's. dim can probably tell more.
7:36:19
ljavorsk
jdz, Hmm I don't know what is known-good state, actually this is my first package so I'm learning about packaging on it. Not to mention the lisp :D never seen it before
7:37:12
ljavorsk
A lot of stuff you write here is new for me, so I apologize if I don't understand correctly
7:43:15
jdz
ljavorsk: Maybe you can look into how Golang applications are packaged; as far as I know Go code can use libraries from git repositories (at specific branches/commits).