@Christophe: thanks, your hint helped. @B Smith-Mannschott:
> Questions about how best to optimize clojure code to approach java > performance have come up with fair regularity in the past. You might > find some good ideas if you search through the archives a bit. I see. As I said before (OP), I believe that the docs, to a certain extent, imply that Clojure is (or should be) as performant as Java. If the same level of performance cannot be obtained (at least in some cases) it should be pointed out. This would set up more realistic expectations for Clojure's users and avoid unneeded discussion. Otherwise you end up thinking you're doing something wrong because your code is so slow and you write posts trying to understand how to write better code. > This isn't always possible though, but that's where Clojure's Java > interop and a little pragmatism comes in: You've got there a nice > piece of Java code that does what you need and it's fast too. If you > want that speed from your Clojure code, don't waste time optimizing > the Clojure, just call the java implementation. > (I guess I'm not much of a purist.) That's exactly my solution. But, again, I believe the docs should be corrected so that people don't waste their time trying to hopelessly optimize their code. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
