Yoshinori, > I'm going to use clojure 1.3. > What should we do, when we're trying to do things like we've been doing with > clojure 1.2 and contrib 1.2? > Such as things with contrib.io, contrib.duck-stream, contrib.string. > > For example, to get lines in a file as a list of strings and do some > modification for each line, > I've been doing: > (map > some-modification > (clojure.contrib.duck-streams/read-lines "a-path-name")) > . > > 1) Use other functions using *in* in clojure 1.3, with binding *in* to a > file reader. > 2) Use the contrib1.2 compiled for clojure 1.3. > 3) Use other libraries derived from contrib 1.2. > > When we're trying to port large sources of clojure 1.2 for clojure 1.3, I > guess we should take 2). > But I want to know what should we do with new developments after now.
As you might know, the monolithic clojure contrib from 1.2 got split into many independent contrib projects. The changes are quite well documented here - http://dev.clojure.org/display/design/Where+Did+Clojure.Contrib+Go http://dev.clojure.org/display/doc/Clojure+Contrib To replace clojure.contrib.duck-streams, you might need to take a look at clojure.java.io which is now in clojure core itself. Regards, BG -- Baishampayan Ghose b.ghose at gmail.com -- 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
