freenode/#lisp - IRC Chatlog
Search
13:05:05
Colleen
See 'help about' for general information. Try 'help X' to search for or retrieve information about a command.
13:05:30
Colleen
I found the following commands: 8, get, mop, say, set, clhs, deny, help, roll, tell
13:05:51
Colleen
Command Syntax: roll &OPTIONAL (SIZE 6) (TIMES 1)
Documentation: Roll some dice. Note that this is not provided with the intention of providing gambling means.
13:06:18
Kevslinger
Is it weird that I thought the roll command would make her roll over, similar to the trick you teach a dog to do
13:07:50
Colleen
Clhs: meanings for + http://www.lispworks.com/documentation/HyperSpec/Body/a_pl.htm
13:18:42
Shinmera
Note that you can ask Colleen for the time as it should be for /users/, not /places/, but in order to do so the person needs a profile.
13:49:07
rme
My flight from Malaga was delayed so I missed my connecting flight in Paris. So, hi from a hotel in Roissy-en-France.
14:01:10
Bike
asked this last night but, does anyone know where slime decides what to print in the minibuffer for a function's lambda list
14:03:30
Bike
there's only one place in slime.el that uses swank:operator-arglist but it doesn't do any further processing
14:32:26
Xof
incidentally, on the question of "why would anyone want to subclass method combination anyway?", I'm not sure! But I do wonder whether a more declarative, less arbitrary-code thing might be able to allow compute-effective-method to do some kind of smart caching
14:32:51
Xof
or rather, the class of the method combination could inform compute-effective-method whether smart caching was allowed or not
14:34:17
Bike
compute-effective-method already turns a second value of extra information, it could include a cachep specification
14:34:33
Bike
cacheablep. of course define-method-combination would have to be altered to allow specifying an em can't be cached
14:35:53
Bike
that kind of ties into the question of how effective methods are actually used, which is sort of its own can of worms
15:37:56
trn
beach: If you remember the Multics system ... https://ban.ai/multics/ ... I made an semi-official announcement (https://lobste.rs/s/4ktahz/ban_ai_s_public_access_multics_system) and yesterday hit about 100 simultaneous users online poking around and nothing broke, though it's a ghost town today.
15:41:16
Kevslinger
phoe: I started with Phoeland but couldn’t find anything. Turns out the land of phoe works just as well :)
15:52:25
trn
beach: I'm working on a a web maintenance panel that will to the system with a WebSocket - so you can watch the blinkenlights of the actual system change the image on the panel that is the background of the web site. :)
16:03:34
trn
For the panel, it uses a lot more bandwidth than I expected it to and it can get lagged, even with compression. So now I'm working on a UDP-based protocol.
16:11:48
trn
I'm likely going to use a 6180 panel like that, because the newer the machines got, the less lights they had, and the more you were expected to look at an operator console.
16:13:49
trn
Probably, the later DPS series of machines looked more like standard racks and the half-sized ones looked like freezers :(
16:15:57
trn
On the 6180 and others I've seen and read the more interesting panels were on the inside of the cabinet doors
16:15:59
trn
https://i.pinimg.com/736x/68/0b/91/680b91e3907ce97558f3b3cc9c888243--evolution-s.jpg etc
16:29:18
trn
It's sort of interesting to me that Honeywell absolutely refused to the idea of a bus in their larger system, and the whole 'bus' was sort of a dirty word - they even abused the 'multiplexer' terminology to avoid 'bus' because they did everything point to point for latency and performance reasons.
16:30:40
trn
Yeah, it's sort of crazy, so attaching 8 CPU's to 8 IOM's needs 64 ports dedicated to that.
16:32:02
trn
The virtual machines 'wiring' code makes this all so much easier than setting these machines up in real life, I'd imagine :)
16:32:53
beach
trn: I need to go help my (admittedly small) family. We just came home from a week at ELS and there is much work to catch up on.
16:33:30
trn
I'll come back and bother you all later - on my todo list is to get the original ITS maclisp ELIZA and SHRDLU code working on multics :)
18:32:58
makomo
i'm looking at the postmodern library for postgresql. can someone tell me the rationale for the global *database* variable instead of having a database parameter in every function?
18:33:57
makomo
well, i know that global variables in lisp aren't the same thing as in other languages
18:34:57
makomo
one thing that isn't clear to me yet is, how does multithreading interact with dynamic scope?
18:34:58
jackdaniel
it may get tedious to carry all contextual varibles to each call of every function (even if function itself doesn't use database at all)
18:35:42
makomo
for example, one thread wants to call the api with one database object, another with another database object
18:35:47
jackdaniel
usually (because there are no threads in CL standard), dynamic bindings are shallow, that means they are not "inherited" from the parent thread (global values are taken)
18:36:15
jackdaniel
I'd recommend reading bordeaux-threads documentation which gives some examples how to do that (and that's basically what implementations do)