freenode/#lisp - IRC Chatlog
Search
13:58:06
jmercouris
but you'll have trouble distributing a compiled application with quri since it loads a data file from an asdf system relative path
14:01:07
patrixl
noted for the suggestion to use quri, it won't solve my immediate problem though ;)
14:01:31
patrixl
filed an issue in Radiance anyway, if puri can't be updated easily then perhaps Radiance can work around it
14:02:26
jmercouris
you might look at where QL is loading Puri from and then you will be able to see how easily it can be updated
14:02:49
jmercouris
to use Radiance you had to add Shinmera's QL dist anyway, so he could easily patch it and provide a different version on his dist
14:06:20
patrixl
AFAIK it's a perfectly valid way of encoding arrays in parameters, when you're not using json to pass data around but x-www-form-urlencoded
14:06:37
patrixl
now whether that should be used as GET or only on POST requests, is another question, I may be doing it wrong lol
14:12:27
patrixl
hmm not a bad idea, it might allow me to remove even more Javascript from my page.. thanks jmercouris
17:18:35
leotaku
I am having some trouble with sbcl, maybe someone here is willing to help. Essentially "(eq (intern "foo") '|foo|)" returns true when I interactively eval the code, but false when I run it as an executable generated by asdf or "sb-ext:save-lisp-and-die".
17:24:28
ck_
the code you saved does not define the symbol before that code is run? I'm not too familiar with sbcl internals, but I would guess that '|foo| gets READ into a different package than what surrounds the (intern "foo") during evaluation
17:30:34
leotaku
ck_: That would make sense, yeah. Any way I can ensure that both the literal symbol and the intern are in the same package?
18:01:53
beach
rdh: The typical place is ~/quicklisp/local-projects. And they are not packages, they are systems.
18:13:21
beach
rdh: Oh, I mean that location for your own projects. Quicklisp will put them where it wants to when you install them with ql:quickload.
18:21:59
rdh
beach, just being that im new to lisp... i don't want things doing work for me, when i don't understand what it's doing.
18:22:44
beach
Anyway, I am off to spend time with my (admittedly small) family. I am sure there are others around to help you in case you need it.
20:57:36
Elronnd
has there been any research on representing lisp programs with something other than sexprs?
20:59:12
White_Flame
there's some experiments with The Forced Indentation of Code to replace parens, too
21:03:22
Fare
Elronnd, Racketeers have a large variety of experiments with alternate syntaxes, from plain old parsers to systems that allow you to do macros with infix syntax.
21:17:56
jackdaniel
Elronnd: I've read that dylan was originally planned to use sexps but they have settled with syntax more similar to c++
22:18:41
aeth
Elronnd, jackdaniel: I wonder why attempts like that didn't wind up going with a system like t-expressions (obviously not exactly like them since Python wasn't trendy in the 90s). https://srfi.schemers.org/srfi-110/srfi-110.html
22:29:40
oni-on-ion
it feels like it would be extra work for the brain. like using google translate to chat
23:03:54
mfiano
Can anyone confirm that (ql:quickload :trivia) does not compile cleanly with the release in the latest QL dist? I'm getting an undefined variable, which probably means something is not going to work at runtime. Curious how a non-style warning slipped through QL though.
23:15:11
mfiano
Looks like a regression fix was committed 6 days ago, which looks like it touches the affected issue. I'm more curious what version of SBCL Xach is using, and how the version would affect this particular undefined variable compiling without a warning.