freenode/#lisp - IRC Chatlog
Search
3:19:12
Oladon
I find myself needing to write a new combination Markdown (probably Commonmark?) + BBCode parser. What's the best approach, architecture/organization-wise, to ensure maximum utility for others while still attaining my aim of a combination parser?
4:32:53
gjulio__
Hey is anyone willing to share a snippet of a .gitattributes file for handling control-m line endings in a *.lisp file? I've been trying a million tactics and I can't seem to resolve the problem.
5:03:48
gjulio__
i solved it. added *.lisp text eol=crlf to .gitattributes. then added (add-hook 'before-save-hook 'delete-trailing-whitespace) to .emacs and then created new files, moved my lisp file to the new file, added the new file to my git repo, and now it's working. it seems like the *.lisp text eol=crlf stuff isn't retroactive. maybe i'm wrong?
5:11:03
gjulio__
not sure. i did edit parts of the file on a different computer that was windows, maybe it's from that?
5:39:14
fe[nl]ix
gjulio__: convert all CRLF line endings to LF and configure your Windows editors to use LF as well
5:40:16
gjulio__
thanks. i'm usually using linux, but i'll keep that in mind if i need to switch back.
13:40:08
jcowan
What are the most common use cases for the syntaxes #n= and #n#, as opposed to the data structures they represent? Is it genuinely common to serialize such things as S-exprssions?
13:40:57
beach
For example, if I have an application with some internal structured data, I use it as a format on disk.
13:41:36
jcowan
beach: thanks. jackdaniel: I didn't mean in code, but that usage is new to me, so I'm glad to see it.
13:41:37
beach
jcowan: Recently, the ASTs produced by the SICL compiler are saved like that, thereby producing FASL files .
13:52:42
beach
jcowan: Here is an example. It is the AST for (defclass t () (:metaclass built-in-class)): http://metamodular.com/SICL/t-defclass.fasl.
14:00:53
beach
In both cases, I use the character `[' as a reader macro. It takes a name of a class and a bunch of initargs, just like the protocol dictates.
14:01:00
phoe
but all that's just a fancy pretty-printed S-expression with *print-circle* being true
14:03:07
beach
It creates a structure that is entirely isomorphic to the original one that was saved.
14:10:10
phoe
how do you map concrete classes to protocol classes? I assume that GSHARP-BUFFER:BUFFER is a protocol class