On Sun, Mar 17, 2013 at 6:07 PM, vemv <[email protected]> wrote:

> Reading a raw string stored in a file is already trivial :)
>

I'm aware that one can store a raw string in a file.  But in many
instances, this would be absurd.  For the kind of rapid interactive
development we have in Clojure, we don't necessarily want every single SQL
query in a separate file.  Similarly, nobody wants to store every regexp in
a separate file.  Actually, regexps are a great example, because the
Clojure reader handles them specially so they don't have to deal quite as
much with escaping as if they were ordinary strings.  I just want that kind
of capability for my own library.

I belive that data is the ultimate DSL anyway - it allows one to express
> arbitrarily specific information in an extensible way. Interleaving code
> and data (as some languages' DSL facilities foster) is inherently complex
> (and limited).
>

Clojure's edn format is convenient for many things, but it has its own set
of limitations and there's nothing "ultimate" about it.  I don't see anyone
proposing that regexps should be replaced by a Clojure-data DSL.  Some DSLs
are based on a really handy notation that has been in use by computer
scientists and/or mathematicians for decades or longer.  Trying to
shoe-horn these convenient notations into something that looks like Clojure
is not always the right way to go.

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to