> > Just guessing, but is it something to do with this (from the docstring > > of parse-seq)? > > > "it will be run in a separate thread and be allowed to get > > ahead by queue-size items, which defaults to maxint".
As I've figured it out, when there's XPP on the classpath, and I'm using it, the code that does the parsing is entirely different and does not involve a separate thread (see with_pull.clj). The parser sits and waits for events to be requested from the lazy seq. > Finally, you might want to be able to walk an XML document larger > than would fit in memory. I'm not sure if lazy-xml has ever been > able to do this as it would need to be vigilant about not > retaining the root of the returned document tree. I was under the impression that if the client was careful to lose the nodes' parents, they would be free for garbage collection, as well as previous siblings. The point is to first navigate to the desired :content lazy seq and then lose all other refs. Then you are in the same position as with any old lazy seq -- you run through it without retaining the head, and things are good. -- 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
