Hi,

have there been any changes how fns with a name and recursion are 
compiled?  One of my projects has a function which does not compile with 
1.7.0-alpha3 anymore, but did fine with 1.6.0.

I tried to create a minimal example at 
https://github.com/ska2342/nested-fn-breaks-clojure-17

(I know the function itself is probably stupid, I just wanted to 
demonstrate the case.  I don't know if it even runs.)

Compilation breaks with a java.io.IOException: File name too long


The problem seems to be the combination of

* using a long function name (not a bad thing per se),
* using a rather long name for a local binding (not common in Clojure-land, 
used in my case for documentation of the intent of the anon fn),
* and using a name for the anonymous function (needed for recursion and 
usually a good idea because it improves stacktraces, but maybe you added 
the local binding to the name for exactly that reason).

Regarding the second (long var binding name), my original function uses 
shorter names, but has some nested constructs (for, cond, ...) which seem 
to make the name larger, too.  There is really nothing unusually long there.

Of course, I can work around this by using different names, factoring an 
inner anon function out to a defn and probably in other ways.  I just 
wanted to make sure, that you are aware that problems like this may show up 
and made the change on purpose.


Thanks,
stefan

-- 
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
--- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to