On Jun 20, 2010, at 22:03 , Nicolas Oury wrote: > primitive vs modern might not be the right terminology.
The main issue I see is not that primitives vs boxed I think when it is done right both will be accepted by the community, the main issue I see is the consequences primitives cause when it comes to things like (or actually only I think) loop. That it makes loop that were initialized with primitives only work with primitives even if the functions return other stuff. so a loop that was initialized with (loop [n 1] ...) will only work with an recur that returns a long, if no long is returnd it acts oddly doing (* n 0.5) which would give you 0.5 every where else in clojure will (since it is type casted to a long) 1 there which is a very odd behavior even if it is documented. This adds to the fact that some simple looking functions that don't at all look wrong (like fact provided earlyer) don't work any more even so from the pure logic (without looking into the special rules for loop) it looks right. Regards, Heinz -- 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
