The agreement is signed and in the (snail) mail. Also, I think I found a solution to the original problem that spurred this thread. In the test-is-adapter namespace I have added an expect macro that wraps the standard expect macro with a binding for the test- is specific report-problem function. So now when you want to use test- expect and test-is together, just :use all of test-expect excluding the expect macro, :use the expect macro from the test-is-adapter, :use test-is and you should be good to go. This way you should get the best of both worlds with no destructive global function changes. Go figure I come up with this after reading the entire "clojure modules" thread and starting a solution using deftemplate :)
- Matt On Jun 11, 8:36 am, Stuart Halloway <stuart.hallo...@gmail.com> wrote: > Matt is signing the CA and I will be adding test-expect to contrib. > > Stu > > > > > > > Can I help from the test-is side? Could test-expect be added to > > clojure-contrib? > > -Stuart > > > On Jun 10, 1:36 pm, Matt Clark <matt.clar...@gmail.com> wrote: > >> Thanks for these ideas, I will give them a try tonight and update the > >> adapter namespace with the changes. If anyone knows of a more > >> idiomatic way I could have implemented the problem reporting > >> functionality that would prevent the necessity of these "hacky" > >> solutions, I'm all ears. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
