Re: Odd Java interop behavior

2011-04-26 Thread Ken Wesson
On Tue, Apr 26, 2011 at 2:36 PM, Ken Wesson wrote: > On Tue, Apr 26, 2011 at 2:26 PM, Dave Ray wrote: >> If the "blah blah blah..." is meant to represent a very long file name >> or path, my guess would be that you've bumped up against the Windows >> path limit (260 chars) which can manifest itse

Re: Odd Java interop behavior

2011-04-26 Thread Dave Ray
Ok. But whether it's reasonable or not, it can happen. For example, the project I work on can't be located in a Windows folder deeper than 37 chars long because Swig generates a particularly long Java file. It has no problems writing it, but further down the the build pipeline, javac dies when it t

Re: Odd Java interop behavior

2011-04-26 Thread Aaron Cohen
On Tue, Apr 26, 2011 at 2:36 PM, Ken Wesson wrote: > On Tue, Apr 26, 2011 at 2:26 PM, Dave Ray wrote: >> If the "blah blah blah..." is meant to represent a very long file name >> or path, my guess would be that you've bumped up against the Windows >> path limit (260 chars) which can manifest itse

Re: Odd Java interop behavior

2011-04-26 Thread Ken Wesson
On Tue, Apr 26, 2011 at 2:26 PM, Dave Ray wrote: > If the "blah blah blah..." is meant to represent a very long file name > or path, my guess would be that you've bumped up against the Windows > path limit (260 chars) which can manifest itself in weird ways. I assume that the file name cannot exc

Re: Odd Java interop behavior

2011-04-26 Thread Dave Ray
If the "blah blah blah..." is meant to represent a very long file name or path, my guess would be that you've bumped up against the Windows path limit (260 chars) which can manifest itself in weird ways. See cause 4 here: http://support.microsoft.com/kb/320081 Since you're also having issues i

Re: Odd Java interop behavior

2011-04-26 Thread Jonathan Fischer Friberg
Since you are essentially using java, I think that a clojure bug can be ruled out. Have you checked the drive for errors? On Tue, Apr 26, 2011 at 8:12 PM, Ken Wesson wrote: > Anyone know what is going on here? I'm trying to use my Clojure REPL > to rename a file that's gotten "stuck" on my Windo

Odd Java interop behavior

2011-04-26 Thread Ken Wesson
Anyone know what is going on here? I'm trying to use my Clojure REPL to rename a file that's gotten "stuck" on my Windows box (somehow, both Explorer and the command prompt claim the file isn't found if I try to move, delete, or rename it) but I get this: com.example.isii=> (FileInputStream. (nth