freenode/#lisp - IRC Chatlog
Search
23:52:29
Bike
jmercouris: if they're all named by interned symbols you could, but it's a weird thing to do.
23:52:42
jmercouris
Bike: I'm trying to make it so that users can inspect all variables like in emacs
23:52:56
jmercouris
Bike: this is obviously for the browser, I want it to have that same discoverability of what all confiigurable parameters are
23:53:51
Bike
it's pretty unnatural to have a defvar named by an uninterned symbol, i just tend to name caveats
23:55:31
Bike
that doesn't actually tell you whether the variable is special, as in declared by defvar, but the difference should be mainly academic.
23:56:28
jmercouris
Bike: I'm not strictly interested if by defvar, I just want to be able to have a user query vars and show their resultant docstrings
23:56:49
jmercouris
Bike: speaking of which, could you please tell me what the correct way to docstring a function is?
23:57:03
jmercouris
I've looked at so many different ways to do it, and documentation generators, and I'm really not sure what's right
0:02:18
Bicyclidine
i usually just write an explanation of what i think is relevant. i don't use doxygen type tools.
0:06:59
didi
In LOOP, can I bind (values ...) values as I can destructure lists? Something like (loop for (values a b) = (truncate 42 7) ...)
0:10:25
Bicyclidine
You can do (a b) = (multiple-value-list (truncate ...)) if you don't mind the performance hit.
1:05:58
phoe_
Yes, except in macroexpanders' case, I can think of how one can use these side effects to achieve something.
1:06:44
phoe_
For macros, it's compilation-time / macroexpansion-time computation. For types... hum.
1:08:36
Bicyclidine
the obvious expansion of (defmacro name ll ...body) is (setf (macro-function 'name) (lambda (form env) (destructure ll form env ...body)))
1:08:39
phoe_
I just find it fun that the moment I start typing "(foo" into the REPL, boom, they're printed.
1:32:25
z3t0
I am half way through practical common lisp and am looking for some supplementary material as well
1:35:45
z3t0
I don't really have a lot of free time as a first year engineering student so it's slow going through PCL
1:39:49
PuercoPop
I'm trying to figure out the correct way to message the values returned from alexandria:parse-ordinary-lambda-list to match a call to apply. I know it is bad style, but what would be the correct way to handle optional and keyword arguments being mixed?
1:45:20
beach
PuercoPop: What does it mean to "message" something? And what does it mean to "match a call" to a function?
1:46:11
PuercoPop
Basically I fiasco, a test framework, has this code (apply (name-of (test-of (context-of failure))) (actual-test-arguments-of (context-of failure)))
1:46:41
PuercoPop
with its own parse-lambda-list, which uses a visitor pattern, to get the text arguments of