Library can depend on an older version of itself?

[Michael Bradley, Jr.]

Is there a straightforward way to setup a Clojure library so that it can depend on an older version of itself?

I can think of a couple of ways to do this that seem clunky, but was wondering what approaches (if any) have worked well for other folks. Something involving pomegranate and clojure.tools.namespace?

--

Michael Bradley

@michaelsbradley

[James Reeves]

I don't have any suggestions as to how this might be achieved, I'm afraid, but I am very curious as to why you'd want to do this.

- James

--
--
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
---
You received this message because you are subscribed to the Google Groups "Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojure+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Michael Bradley, Jr.]

I’m writing a parser that will be easier to write with itself, but I want to be able to “freeze” an earlier version that’s passing all the tests (for features implemented so far) and which is implemented quite differently.  The older version can then be used as the basis for the next version, and that version in turn as the basis for the version after next, and so on.

--

Michael Bradley, Jr.

@michaelsbradley

You received this message because you are subscribed to a topic in the Google Groups "Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojure/OFwMQ5apN0Y/unsubscribe.
To unsubscribe from this group and all its topics, send an email to clojure+u...@googlegroups.com.

[Robert Levy]

Since it's just temporary, maybe create a temporary namespace hierarchy with the old version of the compiler. This would be a terrible sin if you intended for that code to stick around but if you promise you will throw away the older version once you don't need it anymore...