Tassilo Horn <tass...@member.fsf.org> writes: > If not, is there better way than inserting gazillions of printlns to > check why and where a function doesn't do the right thing?
Most definitely! Break your functions up into smaller pieces, then write tests for them using test-is. If your functions are hard to test, it's probably because they need to be broken out differently. -Phil --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
