freenode/#lisp - IRC Chatlog
Search
22:35:24
jackdaniel
jcowan: afair it was deliberely released to public domain by authors before ansi standard was accepted
22:36:01
jackdaniel
I think that this is described in detail on one of Kent Pitman website pages (don't remember which)
22:36:05
jcowan
Excellent. The Interlisp group wants to reformat it in Interlisp style now that Interlisp is moving toward ANS CL support.
22:40:02
jcowan
I know that Xach has it online in the original TeX at Github, and the same content is online as HTML at https://mr.gy/ansi-common-lisp
22:41:16
jackdaniel
you may also look for the cleaned up tex source - afair the repository is called clstandard-build on gitlab
22:41:40
jackdaniel
that said you my find it by accessing cvberry.com on internet archive (for some reason domain expired and the site is not up anymore)
8:57:36
splittist
have text with various fonts and colors (sic) displaying with CLIME. Now to do it properly and tidy up (:
9:35:30
lukego
next thing I'm going to hack is ACCEPT by clicking on a presentation. probably on monday though. the big question I'm wondering is if we can avoid the (with-output-to-emacs (s) ...) business e.g. could (draw-rectangle ...) automatically initialize the CLIM state without needing that macro? I think it would be invoked on *standard-input* which would be a slime-input-stream. dunno. maybe wrong idea.
9:39:39
easye
Could someone point me to the irc channel where shinmera et. al. hangout (#shinkuma or something?)
9:52:30
edgar-rft
nij: ...the predicate <predicate-name>, which must be a symbol whose global function definition is a one-argument predicate.
10:06:29
beach
nij: Did you watch the panel discussion of ELS2021? Kevin Layer from Franz inc said something quite good. He said something like, it is easy for individual users to have wishes for this or that feature to be added, but we (i.e. the creators of implementations) are responsible for ALL our users.
10:06:30
beach
Plus, users typically don't understand the implications of their wishes on the rest of the system, and it is more likely than not, especially if they are not experienced implementors, to suggest something that would be catastrophic for the overall system, in particular for performance.
10:07:21
nij
I threw that comment out just to see if someone can offer a reason why that's not the case.
10:08:14
beach
nij: So, as a creator or maintainer of a Common Lisp implementation, I feel that it gets really boring to listen to wishes from individual users with no knowledge of language design or compiler design.
10:10:00
nij
As a creator of a CL implementation, do you see why not allowing lambdas in (satisfies..)?
10:11:05
beach
nij: The people who created the standard are probably all individually both smarter and more experienced than I am, and collectively they are totally awesome. I would have to look up the reason just as you would because I can't keep everything in my head. But you can count on nearly every decision of the standard to be well motivated.
10:11:14
no-defun-allowed
As someone who is vaguely maintainer-shaped, I have to wonder how you would interpret a (SATISFIES (LAMBDA ...)) form.
10:11:18
splittist
CLIM/McCLIM question - what is the height of an empty string? Different backends seem to have different answers: 0 or line height. (I guess this is the same as: what is the height of #\Newline?)
10:11:58
no-defun-allowed
Would it be as if the name was COERCEd to a function, possibly invoking COMPILE?