libera/#commonlisp - IRC Chatlog
Search
13:32:01
mrcom
Just looked at the HT docs, and it says the default Taskmaster creates a thread for each connection. So killing a thread won't run out of task handlers.
18:46:57
pjb
alethkit: but even the implementations targetting POSIX systems, they mostly run on bare hardware, with just a few dependencies in libc and a kernel… They could easily be made to run on raw bare hardware.
19:05:45
rotateq
alethkit: SBCL is an implementation, ran from the start on bare metal afaik and compiles natively.
19:07:09
Bike
"bare metal" can also mean independently of an operating system, and sbcl can't do that
19:13:24
Nilby
I don't think it's even close to easy to run SBCL without an OS. It's tough to get it to be usable with just a kernel. Mezzano is far ahead in that regard.
19:18:22
alethkit
So getting SBCL to work in Mezzano, or getting SBCL to work for embedded development via Mezzano's compiler?
19:40:34
mrcom
Just saw Eitaro Fukamachi's web post (dated today), and he's saying that Hunchentoot is creating a thread per request. HT docs I just saw say, by default, it's per connection. Tom-A-to/Tom-AH-to, outdated info, or ???.
19:43:01
mrcom
n/m--Tom-A-to/Tom-AH-to. Article later goes into detail, says "...creates a new thread when accepting a connection,... terminates the thread when it's disconnected."
20:42:11
dlowe
though I think about having two compilers sharing the same image and it makes my brain hurt
0:46:03
zacque
Hi, I don't get the OBJECT parameter in PPRINT-LOGICAL-BLOCK. It's stated that "The object is normally a list that the body forms are responsible for printing." Yet, it makes no difference if I pass a list object or NIL into it
0:54:29
specbot
Examples of using the Pretty Printer: http://www.lispworks.com/reference/HyperSpec/Body/22_bb.htm
0:56:19
zacque
Ah, makes sense! I was confused by the first SIMPLE-PPRINT-DEFUN example, didn't notice that PPRINT-POP is used in the PPRINT-LET example