freenode/#lisp - IRC Chatlog
Search
22:58:58
fiddlerwoaroof
I vaguely remember someone talking about loading every system distributed with Quicklisp into a single image as a sanity check of sorts
23:31:18
fiddlerwoaroof
Xach: makes sense, I'd be interested in a "stable" dist that only accepts pure lisp packages (no FFI) that can be loaded together
23:32:20
fiddlerwoaroof
I've occasionally tried to figure out how to host my own diet, for reasons, but never really seriously enough to have anything to show
23:33:26
Xach
fiddlerwoaroof: i had hoped that dists would be very common, with people hosting lispworks-only software, or other thematic dists, but a combination between a lack of interest and a lack of documentation and probably other factors has made it not happen yet
23:45:53
charles`
I would think if you were a company writing internal libraries you would want to host your own dist for those.
23:48:34
aeth
fiddlerwoaroof: there is a distinction... outside of systems with X Windows (where CLX exists and can use the protocol), you can't do anything graphical without some degree of FFI
23:49:01
aeth
But if someone made a graphical toolkit on top of just the OSes themselves, then it would be useful.
23:51:12
aeth
Xach: Sorry, I'm unclear, I mean zero distributed foreign dependencies. So if someone wants to just wrap the WinAPI, then that should be OK, to complement something like CLX, but OS-agnostic.
23:51:51
aeth
As opposed to something like cl-sdl2 where you have to have SDL2, a giant C dependency, at some point.
23:52:51
Xach
Oh. Well, I'm thinking of users with semi-exotic platforms, where binding to some "it's installed everywhere! (if you use linux/windows/macos)" is a failure
7:41:55
fiddlerwoaroof
Xach/aeth: yeah, my goal would be to include things like Alexandria that should reasonably be expected to be usable anywhere
7:42:59
fiddlerwoaroof
quicklisp or ultralisp would be used for things like clim that require functionality beyond the standard
7:45:15
aeth
well, more clim backends (that don't currently exist?) than clim, since clim itself would be fine
9:14:14
ludston
Is there a quick and dirty way in CLOS to wrap a struct with another struct that proxies through all of the accessors on the wrapped struct?
9:15:06
jeosol
beach: I am reading your paper. The template is used is the suggested one for ELS. Do you have a link for the template handy. I think I have seen slightly different designs.
9:19:37
beach
jeosol: I just copy my old papers and modify them. It is entirely possible that my template is out of date.
9:19:39
jeosol
I am taken by the comment in the abstract that presence of optional and/or keyword argument impacts function call performance
9:20:08
jeosol
oh ok. I recally having seen a different format. No worries, I'd pick one from the site and create a base template folder
9:22:51
jeosol
by "taken by", I mean understand how bad design may reduce performance, and certain styles are better. I'd have to read everything to get the full gist
9:24:41
beach
I don't know how much you know about the design of a typical Common Lisp system, but keyword parameter must typically be parsed by the callee for each call. The rules are complicated. For example, the same keyword argument may occur more than once, and it's the first one that counts.
9:25:37
beach
And if :ALLOW-OTHER-KEYS <true> occurs somewhere in the argument list, then no error should be signaled for unrecognized keyword/argument pairs.
9:25:43
jeosol
No, I am not a compiler guy, at all, I am mostly application focused, i.e., using the language. I have only started getting deep in the internals as I try to improve performance and get better design
9:26:26
beach
Well, as the paper says, compiler macros are often used to avoid this parsing in many cases.