> --
> You received this message because you are subscribed to the Google
> Groups "Clojure" group.
> To post to this group, send email to clo...@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+u...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/clojure?hl=en
--
Omnem crede diem tibi diluxisse supremum.
How about: [org.clojure/data.json "0.1.1"] (formerly clojure.contrib.json)?
--
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/
Railo Technologies, Inc. -- http://www.getrailo.com/
"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)
http://dev.clojure.org/display/design/Contrib+Library+Names
c.c.string is not included in this list.
Is there any plans to go to modular contrib (string.incubator,
tools.string, etc.)?
--
Name: OGINO Masanori (荻野 雅紀)
E-mail: masanor...@gmail.com
>> Similar question: where is clojure.contrib.string for 1.3?
> +1
>
> http://dev.clojure.org/display/design/Contrib+Library+Names
> c.c.string is not included in this list.
> Is there any plans to go to modular contrib (string.incubator,
> tools.string, etc.)?
FWIW, many functions from c.c.string were migrated to the core clojure.string namespace starting in Clojure v1.2.0:
http://clojure.github.com/clojure/clojure.string-api.html
- Chas
Will the rest be migrated in clojure.string until 1.3 release date?
If not, probably we need modular c.c.string for performance-sensitive
codes, or less (apply str ...string manipulation...) without getting
rid of seq abstraction.
Thanks.
Cheers,
Aaron Bedra
--
Clojure/core
http://clojure.com