Hi Michael, Thanks for the response. You are likely right about that. While none of them actually look very large, The function is built-up using macros. I will cross check if I can split it. I am using PigPen which makes heavy use of macros and due to some of the semantics of how it is able to handle closures, I am forced to use Macros to build my functions. I was clearly able to identify the change I made which triggered the above error. The change I made seems very benign(the change can't explain the byte-code bloat). I will try to split the functions as much as I can and see if it makes the difference.
Thanks, Sunil. On Sun, Oct 5, 2014 at 5:18 PM, Michael Klishin <michael.s.klis...@gmail.com > wrote: > > > On 5 October 2014 at 15:20:36, Sunil S Nandihalli ( > sunil.nandiha...@gmail.com) wrote: > > I am getting class file too-large errors when I compile the clojure > > file. Do you have pointers as to how one can identify the offending > > piece of code? > > You likely have a giant function somewhere. Split it into multiple small > ones. > -- > @michaelklishin, github.com/michaelklishin > -- 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.
