Best would be to act as professionnal: - try to convince your new boss of the benefits of using clojure from a business point of view. - if this fail, either go back to writing java or quit.
But do not try to abuse your boss and company by developping in clojure behind the scene and deliver some crappy generated java. This would be a legitimate reason to be fired. On 29 sep, 20:09, Dennis Crenshaw <crensha...@gmail.com> wrote: > I'm in a bit of a bind-- I've written some really nice Clojure code for > dealing with Genomic sequences that works as well or better than the > reference implementation we currently use where I work. However, the the > hierarchy has recently changed and my new boss is requiring me to have all > code in Java (eg. interop is not an option since he wants the source to be > pure Java.) Is there any way to prevent my head exploding from > hand-translating my Clojure code into Java? > > I'm sure it's possible to generate Java source since we heard Rich's amusing > anecdote about using Clojure to write reams of Java boilerplate instead of > doing himself. Is there a precedent or even an existing library for > translation from Clojure into Java source though? I'd like to be able to use > the code I've got without a long, painful devolution. More importantly, I > want to be able to continue developing in Clojure and just compile it to > Java source and check that in. > > Thanks, > Dennis -- 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
