freenode/lisp - IRC Chatlog
Search
17:40:48
|3b|
looks like nibbles has portable implementations of integer functions, so might work on mezzano... don't think i would have used the float functions in 3bz
17:47:28
verisimilitude
Am I to understand there's a library for manipulating PNGs written entirely in Common Lisp, already existing?
17:48:28
verisimilitude
That's interesting; I never looked much, but only saw C bindings. I'll probably focus on some format without a pure Common Lisp solution whenever I get around to manipulating images, then.
17:50:24
verisimilitude
What I meant is, whenever I do finally get around to working with some image file format, I'd prefer to write a Common Lisp library that serves a format where that currently isn't done.
17:50:47
Shinmera
mfiano: |3b|: Xach: I would be more than fine with removing the Osicat dependency in mmap.
17:52:28
Shinmera
The only reason I used osicat was because I was too lazy to do a survey of the necessary constants and types myself.
17:53:27
verisimilitude
I see there's already an implementation of a tar format handler in Common Lisp, although that won't stop me from writing my own at some point; the name I thought of is too good to glance over.
18:02:09
mfiano
Xach: Okay, master now reflects the state before 3bz, and the fast branch is the new one.
21:31:28
ralt
is there an easy way to access an element by name, e.g.: `((:server . "nginx") (:etag . "foo"))` looping through every element looks ugly. Want to get a drakma response header.
22:06:07
ralt
never needed it until now, and now I realize there's a lot of things I could've done better
3:59:16
ck_
tourjin: you can get slime through the emacs package system, for example. Search for "Melpa packages" to set that up
4:00:39
jeosol
Is there a work around to save SBCL from slime (normally do that from the shell). Keep getting this message: "Cannot save core with multiple threads running."
4:08:15
|3b|
you could try killing all worker threads, exiting repl, and saving from *inferior-lisp*
4:52:21
Colleen
Unknown command. Possible matches: 8, time, deny, set, say, mop, get, tell, roll, help,
5:00:19
beach
And what does your interpreter have to do with CLISP? Are you trying to copy what they did?
5:05:21
LdBeth
Since a very bare bone lisp interpreter such as ulisp can barely fit into Ardurino chip
5:07:12
fragamus
the interpreter needs to be tiny but the code for common lisp can be on a regular storage device
5:13:42
LdBeth
I don’t get the point, since if a large storage is available there’s no need for a lisp interpreter to load a Common Lisp
5:14:14
fragamus
well the lisp program will be small and won't link to much and won't do a lot of alloc
5:22:22
pjb
fragamus: lisp.run is in a place that depends on the installation of clisp. For example, it can be something like: /usr/local/lib/clisp-2.49.93+/base/lisp.run
5:22:46
pjb
fragamus: The best is to get the sources of clisp and to configure and compile them yourself.
5:23:48
pjb
fragamus: clisp implementation is made much more complex than what you want, because it has to deal with two stacks: a normal C stack, and a lisp VM stack.
5:24:31
pjb
fragamus: see https://clisp.sourceforge.io/impnotes/ and https://clisp.sourceforge.io/impnotes/internals.html
5:28:02
tourjn
alt-x package-list-packages show me several slimes which is most popular one? I have two slim-mode two slime and a lot of slime-*.