Thanks for all the responses!
> http://dishevelled.net/Generating-Clojure-import-lines-using-SLIME.html
Hey that's making life TOO easy! I especially love that it has REPL lookup.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group
Timothy Pratley writes:
> I've found myself a few times in a situation where I'm banging some
> java code into clojure, and the java source uses import foo.* blah.*
> bar.* How do other people do this?
If there's a lot of stuff I have to import I use Mark's nifty addition
to SLIME:
http://dis
Any half-way decent IDE should have a shortcut for resolving wildcard
imports to be fully-qualified.
On Feb 2, 7:31 pm, Timothy Pratley wrote:
> Hi,
>
> I've found myself a few times in a situation where I'm banging some
> java code into clojure, and the java source uses import foo.* blah.*
> bar
Whenever I had to do this, I put the java code in a separate java
file in IntelliJ, and let it figure out the list of imports.
I then paste them into clojure.
Works well since I also use IntelliJ for clojure anyway.
On Tue, Feb 2, 2010 at 10:31 PM, Timothy Pratley
wrote:
> Hi,
>
> I've found my
I've found myself a few times in a situation where I'm banging some
java code into clojure, and the java source uses import foo.* blah.*
bar.* Now Clojure requires explicit class naming (which I fully
support) so I end up spending a good slice of time googling "java
SomeWierdClass someapi" to ge
Hi,
I've found myself a few times in a situation where I'm banging some
java code into clojure, and the java source uses import foo.* blah.*
bar.* Now Clojure requires explicit class naming (which I fully
support) so I end up spending a good slice of time googling "java
SomeWierdClass someapi" t
