to me symmetry is important. That is, consistency ... because it helps people know where to look.
So, if slurp is in the core, spit should be in the core (but why not just use python's way more typical convention of "read() and "write()". Another example I recently saw is that "(nth)" is in the core, but "(pos)" (something I think of as nth's inverse) for "position" is something you need to go to java for (.indexOf). To me, get nth out, or put pos in. So stuff people put in contrib to specifically fill a gap in core, should potentially have a special ticket category and be on the fast track for discussions. This stuff might not seem like a big deal to the seasoned clojurian ... indeed, weathering such might be the battle scars of the persistent (to mix several metaphors and puns). But it seems like a type of barrier that can go away for future newbies (and current ones like me). ... and the answer that I hear a lot: "write a macro or function" only helps me. And where would I put it for others? In contrib? Ah ha! maybe for now, but what next? - Eli On Tue, May 12, 2009 at 6:04 PM, Phil Hagelberg <p...@hagelb.org> wrote: > ntrib is a bucket-o-code. Since we as a > community don't have any widely-accepted mechanisms for dependency > resolution, there's a quite understandable motivation to put useful > libraries in contrib so that other clojure hackers can make use of them > with minimal hassle. > --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
