> Again, there'd have to be a staggering further benefit from the change > than just "the clojure.core code looks cleaner in github" or even "the > code is a bit easier to maintain in the future". I'm not sure that > even massive increases in code maintainability alone suffice for > something like this. A major, massively end-user-useful new feature > that's nigh-impossible to implement otherwise that can then be > implemented *might* suffice. >
I think the point was not to criticize you at all (nobody have to read every post in the archive) but just to point the fact that this debate was somehow already behind us. It has been already debated a lot with pretty good points on each side. (The concerns you are expressing are good points, as are the answers in this thread and the preceeding on the subject.) For the specific problem you are facing, I would advise to go through your code looking for number literal and replacing each number nnnn by nnnnN. (ex 15 ---> 15N). As boxedness is contagious, you probably won't have to change much more to solve compatibility issues with 1.3. If you find other specific problems, it would be great to post them: we will need a good compilation of tips to convert numerical code from 1.2 to 1.3. Best, Nicolas, -- 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
