freenode/#lisp - IRC Chatlog
Search
17:16:23
rme
Presumably this is because the spec says "If the at-sign modifier is used with ~<...~:>, the entire remaining argument list is passed to the directive as its argument."
17:26:59
pjb
The way ~< is specified is clear: the argument is mandatory (it's the second argument to pprint-logical-block).
17:34:40
rme
Yes, so ccl is rightfully expecting an argument, and is right to complain about its absence.
17:42:11
rme
I'm starting to think ccl is probably wrong here. If the @ modifier is present, it seems like it ought to be OK if the "remaining argument list" is nil.
18:09:23
stacksmith
pjb: what's the deal with prog2? CLHS says "prog2 evaluates first-form, then second-form, and then forms, yielding as its only value the primary value yielded by first-form." How does that differ from prog1?
18:26:00
pjb
The thing is that since the specification is not formal, and is known to contain bugs, some level of consensual interpretation is left to the implementations. But it is better if all implementors agree on thos litigious points. Unfortunately, on some important parts, they don't. Eg. they could agree on how to do pathnames (both physical and logical) on POSIX systems, but they don't. :-(
18:30:21
stacksmith
pjb: oh are you saying that they indeed do return 2? I read it as 'I wish they would all return 2' ...
18:31:30
stacksmith
loli: I know. I was asking pjb to clarify a statement earlier that I misunderstood.
19:44:48
puchacz
hi; slime on slow device please. I am getting [Interrupted: time limit exhausted] on fuzzy completion
20:15:54
jackdaniel
I've wrote some rendering approximation illustrations with McCLIM: http://hellsgate.pl/files/c885c815 (I'll make it one of clim-examples after adding some interactivity to it)
20:36:05
flip214
puchacz: well, why not do the auto-completion against a faster system, and just run the code on the slow target system anyway?
23:35:14
malice
The problem is, it somehow does not work on the emacs level; indentation bugs and C-c C-c invoked to compile it fails somehow
23:35:30
malice
it looks as it treated the comment as the code, even though string does not end prematurely
23:38:21
pjb
malice: when you have forms or strings that are too big, font-locking can have difficulties processing them.
2:41:14
nydel
i don't think i've ever seriously used cmucl. i might be interested to try out CLX its built-in x11 gui interface, anyone used it to positive or negative experience?
2:49:28
Bike
and programming with clx is equivalent to programming with xlib, that is to say, extraordinarily unpleasant
4:43:26
beach
Lycurgus: So now that you know about all the activities toward a Lisp OS, have you decided to help out with some project?
4:48:44
Lycurgus
the lisp image portion would be the "upper part" of MCP married to a SSI linux kernel