On Mon, Jul 6, 2009 at 7:50 PM, Richard Newman <holyg...@gmail.com> wrote:
> > > Since it's not apparently a simple bug in my function above, but > > something about a combination of that version of that function and > > some other part of my code, I can't think of a way to track the > > cause down short of the very tedious method of commenting out > > functions or replacing them with dummy functions (if they're called > > by the above function) and seeing which one has the property that > > commenting it out or dummy-izing it makes the error go away. > > > > That will probably take all afternoon, unfortunately; there are > > dozens of functions and over 1600 lines of code in that source file. > > Have you tried simpler things like splitting the offending function > into a separate namespace, or seeing what happens with (or without) > AOT compilation? I didn't get around to that because I accidentally fixed the bug somehow. I moved a few functions that I realized were general purpose over to a separate utils project and recompiled everything. The source file with the problem contained some of the functions I moved, and now loads correctly. It looks like one of those functions conflicted in some way with the newer version of the function posted to this thread, though I'm baffled as to how or why. None were directly called by it, or otherwise directly referenced by it, nor vice versa. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
