Jup, that solved the problem. Lesson learned. Thanks :) Alf
On Thu, Sep 22, 2011 at 17:54, Meikel Brandmeyer (kotarak) <m...@kotka.de> wrote: > Hi, > > Am Donnerstag, 22. September 2011 17:43:30 UTC+2 schrieb Alf: >> >> What am I doing wrong here, will filter/remove or something else give >> StackOverflowError when used incorrectly? > > Yes. You pile lazy seq on lazy seq on lazy seq on .... and then realise the > first element. This kicks off a cascade which finally causes the stack > overflow when your lazy seq pile is large enough. > > Put a doall around the remove. This will realise the seq immediatelly and > the cascade cannot happen. So it should solve the issue. > > Sincerely > Meikel > > > > -- > 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 -- 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
