freenode/#lisp - IRC Chatlog
Search
4:21:20
beach
So I take it nobody wants to appear in the Acknowledgments section of this paper: http://metamodular.com/SICL/representing-method-combinations.pdf
6:26:31
no-defun-allowed
It appears that this function definition (rather, the documentation string) prevents C-c C-c from working correctly: https://pastebin.com/h8sHNTzf
6:31:15
no-defun-allowed
That appears to compile from (with-locked-box ...) in the documentation string wherever I C-c C-c from, which fails spectacularly.
6:32:04
trittweiler
the answer is most likely "don't write docstrings like that", i.e. intend inner code blocks by at least 1 space
6:57:03
beach
no-defun-allowed: You can use the trick with #.(format nil "...") so that in the format control you can ignore indented lines.
6:57:38
beach
No version of the paper. Thanks to MetaYan and slyrus for the feedback: http://metamodular.com/SICL/representing-method-combinations.pdf
7:57:54
splittist
no-defun-allowed: https://www.gnu.org/software/emacs/manual/html_node/emacs/Left-Margin-Paren.html
11:39:04
p_l
beach: well, it would be nice to appear - but that requires actually having done something for it to happen ;)
12:17:27
phoe
beach: about CCL, "Instead it defines an info vector (disguised as a structure)" - CCL tends to do that a real lot. From what I have noticed, a lot of internal structures in CCL are actually tagged vectors, where the tag tells CCL what kind of a structure that is.
12:22:09
phoe
p_l: nope, it's a different trick that CCL uses. The resulting object still prints like a structure type and has its own distinct type.
12:25:10
phoe
(defstruct (foo (:type vector)) a b c) (type-of (make-foo)) ;=> (SIMPLE-VECTOR 3) on SBCL
12:34:36
phoe
There are things called ivectors and gvectors in CCL that are tagged like I described up above - but, amusingly, CCL's method-combination-info objects are neither of them
12:34:38
montaropdf
I have some strange configuration problem with my common lisp environement. ~/common-lisp/ is not in the asdf registry and some packages seems missing from quicklisp.
12:36:52
montaropdf
Message from quicklisp: You already have the latest version of "quicklisp": 2019-12-27.
12:37:18
montaropdf
Message from the client: The most up-to-date client, version 2020-01-04, is already installed.
12:39:02
phoe
https://github.com/quicklisp/quicklisp-projects/search?utf8=%E2%9C%93&q=informatimago&type= gives me nothing.
12:39:44
phoe
montaropdf: quicklisp/quicklisp-projects on github is the ultimate source of information for what is included in QL.
12:43:05
phoe
on my machine, asdf:*central-registry* ;=> (#P"/home/phoe/.roswell/lisp/quicklisp/quicklisp/")
12:44:02
phoe
maybe that's the cause - if you've installed QL, it likely is set to ~/quicklisp/local-projects/
12:44:36
montaropdf
I just check now and look what I have found: #P"/home/roland/quicklisp/quicklisp/"
12:50:58
montaropdf
So, I will add ~/common-lisp/ to the registry from .sbclrc, seems the best to do.
13:50:31
Demosthenex
can someone recommend an xml lib for outputting graphml? i don't need to parse, just output correct xml
13:53:20
Demosthenex
i thought plump was focused on parsin? i suppose it'd have a method to output somewhere too
13:58:05
beach
phoe: Do you know the reason for that? My guess would be for reasons of bootstrapping, but I am only guessing.
13:59:25
phoe
beach: I do not think so. ivectors and gvectors are used galore even in the bootstrapping process. I think it's just style inconsistency and one could fix easily that someday.
14:01:55
phoe
Large chunks of the method-combination.lisp file are at least 12 years old - we don't have any earlier history.
14:04:44
phoe
Coral/Macintosh/Clozure Common Lisp is an old implementation and I think that's its heritage that we are looking at right now
14:04:59
beach
But it is also possible that it is a bootstrapping problem. If CLOS is "bolted on" the way it is in many Common Lisp implementations, then, at the time you need method combinations, you may not have classes yet.
14:06:30
phoe
that's true as well, since CCL has its own bootstrapping process where method combinations are actually loaded close to the end of the process