8:39:45paule32i don't know other lispsers behavoir
8:39:59shka_perhaps it is the problem, maybe you can ignore this issue
8:40:20shka_there are multiple ways to think about it
8:40:51shka_i personally use cl server side, so i almost never care about binary size
8:41:19_deathif you care so much about hello world applications perhaps C is the answer indeed
8:41:26paule32i have server here, which shall serve / host lisp projects, it has 24 giga byte ram with 2x 2 terra bytes hard disk space, ok, but the stream / makes the different
8:41:28shka_therefore, i have no idea how to reduce it
8:44:05paule32ok, that should not be hard, but i had one eye on it
8:44:06beachpaule32: It seems that no free Common Lisp implementation is organized so as to allow most of the code to be in a shared dynamically-linked library.
8:44:29beachpaule32: I guess the developers have other priorities.
10:47:55smokeink_can't view the listing with all files
11:04:33smokeink_hmm (ql:system-apropos "") seems to return all the systems
11:06:09dschoepesmokeink_: (ql:system-list) will give you that as a normal list instead of just to stdout. you could map ql:quickload over that, I suppose
13:40:24lokeI just upgraded everything (Emacs+QL+SBCL) on a computer on which I haven't done any development in a while. Now, loading SLIME gives me an inetresting error:
13:40:33lokeError finding package for symbol "NOTIFY-DEPRECATED-FUNCTION":
13:40:34loke The name "UIOP/VERSION" does not designate any package.
14:03:16lokephoe: I had. It's just that the SLIME plugin SLIME-ASDF (I'm not even sure what it does or wny I installed it) doesn't work with newer UIOP
14:21:37phoebeach: I made a tiny comment. I hope it's constructive.
14:22:09beachphoe: Thanks. Browsing the logs, I can see that he has done some related work in the past. This one for instance: https://www.hexstreamsoft.com/articles/notes-tips-standard-common-lisp-symbols/cross-references/clhs/figures/
14:56:06oystewhso i have a tree of struct nodes with a list of node children in each node, and a parent pointer in each struct to its parent. when i enter 'root' at the repl (which is a variable pointing to the root node..) i get control stack exhausted
15:26:50phoeand if you want to have a printed representation that does not do circularity by default and does not depend on *print-circle* - do as beach said, define a method for PRINT-OBJECT.
17:24:12dTalFor what seems to me like a super interesting exercise in language design, based entirely around Lispy principles, it doesn't seem to be very widely used or discussed
17:30:14pjbAt least not here, since we're rather monomaniatical about Common Lisp. Try: ##lisp or #yacas?
17:33:33dTalAh, fair enough. Although it looks like there was a succesful effort once upon a time to port Yacas to Common Lisp, sadly lost
17:34:08dTalAt least according to http://hackipedia.org/Languages,%20computer/Lisp/Lisp%20As%20An%20Implementation%20Language%20For%20Computer%20Algebra%20Systems,%20Yacas%20v1.0.55%20%28May%2020,%202003%29.pdf
18:41:51shrdlu68Been a bit busy lately, what's new?
18:52:58MONODAanyone here use caveman to build a RESTful server? I'm trying to figure out how to send a body explaining the error when the client sends an invalid request
18:54:01MONODAthe provided `throw-code` just gives the typical explanation of the error code. it doesn't allow you to provide a body in the response
18:57:47JuanDaughertynormally it would be conditional text in the body as a computed response
18:58:44JuanDaughertyi.e. that's what the whole page returned from the request is
19:00:58JuanDaughertyalternate body is a (seldom used) thing though, i think there is or used to be a tag for it
19:01:45JuanDaughertyand the only lisp REST pkg i've used is restas