> I prefer to use ^{:dynamic true} instead of ^:dynamic, unless you're
> recommending intentionally breaking compatibility with 1.2 so as to
> encourage people to move to 1.3.

What is meant by "breaking compatibility"?  I haven't noticed any
issues using ^:dynamic with 1.2, am I missing something?

Thanks.

On Sat, Sep 3, 2011 at 4:13 PM, Alan Malloy <a...@malloys.org> wrote:
>
> I prefer to use ^{:dynamic true} instead of ^:dynamic, unless you're
> recommending intentionally breaking compatibility with 1.2 so as to
> encourage people to move to 1.3.
>
> On Sep 3, 12:27 pm, Chris Granger <ibdk...@gmail.com> wrote:
> > Hey Folks,
> >
> > With the release of 1.3 growing ever nearer, it's time that we as a
> > community do everything we can to make the migration smooth. In general,
> > this means relatively simple changes to the libs under your control, but I
> > also think we should take this opportunity to do some house cleaning.
> >
> > If you maintain a clojure library (even if "library" just means some random
> > thing up on github that a few people use), please consider doing the
> > following over the next few weeks:
> >
> >    - *Try migrating your lib to 1.3*
> >       - Create a 1.3 branch
> >       - Remove earmuffs around any non-rebound vars
> >       - Add earmuffs to any vars that are rebound using thread-level binding
> >       - Add ^:dynamic to these vars
> >       - If you rely on the built in Numerics, check to see if the new
> >       
> > changes<http://dev.clojure.org/display/doc/Documentation+for+1.3+Numerics>in
> > 1.3 affect you.
> >    - *Do some house cleaning*
> >       - If you are no longer maintaining this library, simply note so at the
> >       top of your Readme. If the reason is that a better alternative has 
> > spring
> >       up, link to it.
> >       - Take a look at your dev dependencies and determine if any of them
> >       should remain in light of the ability to globally install
> > leiningen plugins.
> >       *If you have swank-clojure as a dependency, please remove it*: this
> >       has been the source of numerous issues.
> >
> > None of these are complicated or particularly time consuming, and the impact
> > they will have as people try to migrate forward will be tremendous. Also,
> > don't fall into the trap of thinking "no one could possibly be using this
> > tiny project" - I bet they are and bet they'll want to continue to :)
> >
> > If I've missed some steps, please reply with them. Are there more house
> > cleaning things we should do? Have you run into any other issues migrating
> > to 1.3 (the steps listed here were purely what was necessary for me and the
> > few others I've talked to)?
> >
> > Cheers,
> > Chris.
>
> --
> 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

-- 
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

Reply via email to