freenode/#lisp - IRC Chatlog
Search
22:40:10
no-defun-allowed
fiddlerwoaroof: If it looks vaguely like s-expressions, could a dispatch table technique work for EDN? That might be faster.
22:43:53
contrapunctus
Trying to understand how to emit the IR for CommonDoc. There is documentation for defining the format as a GF with the associated methods, as well as for constructing a document as CLOS objects, but that seems different from what the Scriba parser does - it returns some plists. I could start trying to replicate its output, but I'd feel more confident if I could see some documentation on this subject...
22:44:30
contrapunctus
...hm, maybe I could go through the CommonDoc sources to understand what it expects 🤔
23:51:34
elioat
does anyone know of a way to "pretty print" an s-expression when it is written to a file? I have a function that saves an s-expression to a file to later read it back
23:57:09
Bike
keep in mind that if you pretty print it it's very possible it can't be read back (by CL:READ)
23:59:06
elioat
that's a good point, Bike thanks! -- I'm thinking that a may actually just have a dump function that is for displaying this data in a human friendly manner, and then keep things as is.
4:37:57
iissaacc
whats the go-to library for drawing trees/graphs? looked at a bunch i wondered if anyone had any recommendations for something easy to get going with
4:38:53
iissaacc
doesnt need to be pretty, just so i can easily see the output of my classification experiments
4:45:33
no-defun-allowed
To see a "tree" the way you would expect to see one, you need to tilt your head 45 degrees anti-clockwise (or your monitor 45 degrees clockwise) though.
5:31:37
contrapunctus
So IIUC I can use CommonDoc's document node constructors ( https://commondoc.github.io/docs/nodes.html ) in my parser to emit a tree CommonDoc can read...but I don't understand why Scriba doesn't do that, or what the purpose of the plists it returns is, or where they are documented - https://github.com/CommonDoc/scriba/blob/master/src/parser.lisp
7:36:42
aeth
markasoftware: The most concise way to get a modifiable string out of a literal string is probably to use COPY-SEQ first.
8:02:51
contrapunctus
So if I understand correctly, I can use CommonDoc's document node constructors ( https://commondoc.github.io/docs/nodes.html ) in my parser to emit a tree CommonDoc can use...but why doesn't Scriba do that? What is the purpose of the plists it returns? And where they are documented, if at all? 🤔 https://github.com/CommonDoc/scriba/blob/master/src/parser.lisp