Appreciate the input guys! Can't comment on the technical side or on where the problem might stem, but I'll tell you what I can:
> > > Does the file you are evaluating have more than 65535 characters? Nope. It's about 1400 LOC and not syntactically unique (no unusually long constants, etc.). It's also not the longest ns in the project: the longest is around 2000 LOC and is still evaluating fine. If I had to try find something unusual about the ns, I'd say that it probably :requires more namespaces than others (22). FWIW the file now consistently throwing the problem -seems- to have started throwing the problem after a change in some -other- namespace so perhaps there's a bad interaction happening somewhere? As per the suggestion in the "Clojure for large programs" thread, I pulled some stuff out of the ns and it appears to be evaluating fine again. So, some conclusions/observations: 1. I'm more or less satisfied: if I know I can always work around the problem by using shorter namespaces, I'm happy. 2. While the namespace size seems to be a factor, I'm not convinced that the problem is as linear as "big namespace = problem". I have other namespaces that are larger (in line count, character count, and definitions) that have been evaluating fine without a problem. This problem feels more random/subtle to me. 3. The problem doesn't [only?] seem to be related to the project size as a whole (since I was occasionally receiving this error even when the project was still < 10,000 LOC). 4. There seems to be a discrepancy in behaviour depending on how the compilation is requested: project-wide command-line compilation seems to keep working even when Slime/Swank evaluation fails. 5. Personally I don't have any problem with hard limits (e.g. keep your namespaces/whatever below X lines/definitions/whatever) even if they're aggressive- but I think it'd be preferable to have an error message to point out the limit when it gets hit (if that's indeed what's happening). That's about all I can contribute :) Again, thank you all so much for your time! -- 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
