:content should be a vector rather than a list about enlive HOT 5 CLOSED

I can't quite understand the problem, what are you trying to achieve?

If you want to serialize the data structure, so it will look pretty much like that:

#=(clojure.lang.PersistentHashMap/create {:tag :a, :attrs #=(clojure.lang.PersistentArrayMap/create {:title "Equals si\
gn", :href "/wiki/Equals_sign"}), :content ("=")})

You can read it back and it will evaluate to:

{:content ("="), :attrs {:title "Equals sign", :href "/wiki/Equals_sign"}, :tag :a}

Am I missing something?

from enlive.

Probably I have to cc @jackrusher

from enlive.

Sorry it has taken me so long to reply.

I tend to do loads of exploratory programming using emacs + SLIME/nrepl, quite a bit of which involves scraping/spidering. An example of this might be:

(def symbols
(html/html-resource (java.net.URL. "http://en.wikipedia.org/wiki/List_of_mathematical_symbols")))

(html/select symbols [:table.wikitable :td :a])
;; C-u C-x C-e in emacs to bring the result of evaluating this express into the buffer
;; => ({:tag :a, :attrs {:title "Equals sign", :href "/wiki/Equals_sign"}, :content ("=")} ... )

... which I would then wrap in a (def) form to use as data for whatever program I might be writing at the time.

Sadly, the form returned by (html/select) cannot be used in this way because the reader tries to execute the string at the head of the :content list. In Common Lisp or Scheme, I'd expect the :content list to be quoted to avoid this problem, whereas in Clojure I'd expect the data to be stored in a vector (using vectors literals rather than quoted lists seems like the preferred convention in Clojure).

Thanks for your consideration.

from enlive.

To me it's the difference between readable and evaluable.
The sensible solution seems to just quite the whole thing when you wrap it
into a def -- after all it's a value not a piece code (Code is data but all
data is not ocde.)

(def foo '({:tag :a, :attrs {:title "Equals sign", :href

"/wiki/Equals_sign"}, :content ("=")} ... )))

On Wed, Jan 23, 2013 at 7:15 PM, Jack Rusher [email protected]:

Sorry it has taken me so long to reply.

I tend to do loads of exploratory programming using emacs + SLIME/nrepl,
quite a bit of which involves scraping/spidering. An example of this might
be:

(def symbols

(html/html-resource (java.net.URL. "
http://en.wikipedia.org/wiki/List_of_mathematical_symbols")))

(html/select symbols [:table.wikitable :td :a])
;; C-u C-x C-e in emacs to bring the result of evaluating this express
into the buffer
;; => ({:tag :a, :attrs {:title "Equals sign", :href "/wiki/Equals_sign"},
:content ("=")} ... )

... which I would then wrap in a (def) form to use as data for whatever
program I might be writing at the time.

Sadly, the form returned by (html/select) cannot be used in this way
because the reader tries to execute the string at the head of the :content
list. In Common Lisp or Scheme, I'd expect the :content list to be quoted
to avoid this problem, whereas in Clojure I'd expect the data to be stored
in a vector (using vectors literals rather than quoted lists seems like the
preferred convention in Clojure).

Thanks for your consideration.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50#issuecomment-12613574.

On Clojure http://clj-me.cgrand.net/
Clojure Programming http://clojurebook.com
Training, Consulting & Contracting http://lambdanext.eu/

from enlive.

On 23 Jan, 2013, at 16:00, Christophe Grand [email protected] wrote:

The sensible solution seems to just quite the whole thing when you wrap it
into a def -- after all it's a value not a piece code (Code is data but all
data is not ocde.)

I can, of course, work around this, but what is the advantage of making me do so? That is, why would one not want this data to be usable in this way?

from enlive.