On Thu, Mar 31, 2011 at 05:00, Eli Barzilay <e...@barzilay.org> wrote:
> On Tue, Mar 29, 2011 at 4:43 PM, B Smith-Mannschott wrote:
>> Horrible hack, maybe, but it got me thinking. What you seem to be
>> doing is moving between "code" and "literal" mode by quoting with #.
>> This is a little like traditional quasi-quote...
>>
>> And that got me thinking about Scribble [1] again.  In this
>> context I think of scribble as being sort of an inverse of normal
>> scheme syntax.  In the end, the scribble reader produces the same
>> kind of data structures as the normal scheme reader, but the
>> emphasis is moved from code to textual content. Source is content
>> by default, but you can escape into logic.
>
> This is kind of a good summary of the reader's intended use, beyond
> our documentation system: it's fitting for any kind of code that deals
> with a lot of textual content -- and having a kind of cheap DSLs for
> interacting with other tools by generating source is exactly one of
> the things that you can do with it.  But getting that from the
> scribble documentation will be a little hard -- I wrote a paper on
> just the implementation and use cases of the reader that will be much
> more fitting in this context, with some examples of such uses:
>  http://barzilay.org/misc/scribble-reader.pdf

Thanks very much for the link. I'm enjoying the paper. When I've
addressed my immediate needs (with stringtemplate), I hope to return
to it again in more depth. I have this notion, that an alternate
reader for Clojure in the style of Scribble combined with core
concepts of stringtemplate could make a convenient and yet lispy
templating system for producing non-lisp code and other textual
output.

// Ben

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to