#clojure logs

2013-11-20

00:00justin_smithm0smith: is that error in the target or the debugger?
00:06technomancym0smith: stick a (def myobj local-obj) in the body of your defn (which you should never do in production) and then do stuff like (-> myobj :key1 :key2 :key3) after running it in the repl
00:06technomancy(assuming you can't use tools.trace)
00:07justin_smithanother option is (def debug (atom [])) and in the function (swap! debut conj datastructure)
00:07justin_smiththen you can even examine the data from multiple calls
00:07justin_smith*swap! debug
00:08adhollanderm0smith: are there any Java libs for working with GEDCOM? (have said a couple times in the past few months would get back to working on genealogy)
00:08scottjadhollander: there are 3 0.1 clojure gedcom libraries/wrappers :)
00:09technomancyif you actually have to poke around on something inside the scope of the function (because it's stateful or whatever) inserting a breakpoint-repl is a lot easier than setting up a full stepping debugger
00:09m0smithjustin: when I do "lein run"
00:10technomancyalso why is there no debugger called steppin-razor?
00:10m0smithadhollander: I have a gedcom parser written in clojure I am using
00:11m0smithtechnomancy: breakpoint-repl?
00:11swarthyI remember reading about a macro you can prefix a symbol with, and the prefix is expanded to the current NS. Did I make that up?
00:11technomancym0smith: https://github.com/technomancy/limit-break or something like that
00:12technomancy^ that should work, but there are more polished versions
00:13ysawejhi all
00:13ysawejwhy does deftype say its still in Alpha
00:13ysawejhttps://github.com/clojure/clojure/blob/clojure-1.5.1/src/clj/clojure/core_deftype.clj
00:13ysawejis it really in alpha? or is the documentation not updated?
00:13technomancyhttp://p.hagelb.org/mystery.gif
00:14scottjysawej: because they've never removed alpha notes since they started adding alpha notes
00:15m0smithtechnomancy: Does tools.trace work with cider?
00:16technomancym0smith: sure
00:16technomancyI'm working on some mad haxx to make it more convenient, but it works fine as is
00:18m0smithI even had it in my profiles.clj but forgot about it
00:18m0smithtools.trace I mean
00:20technomancyit's good stuff
00:20technomancycould be kinda overwhelming in spewage though
00:21coventrym0smith: https://github.com/timvisher/what-does-tools-trace-do/blob/master/src/what_does_tools_trace_do/core.clj
00:21technomancyworth getting acquainted with though
00:21ysawejscottj, i see.. it would be nice to remove them, as it scares Clojure starters to think the language is not as matured
00:21coventrym0smith: Also, <https://github.com/coventry/troncle&gt;, but it doesn't work with cider, at this point.
00:22technomancym0smith: in particular trace-vars is what I recommend
00:23technomancycoventry: ooh, nice thorough readme
00:23technomancyneed to take a closer look at that
00:23technomancycoventry: looks vaguely related to guzheng; have you seen that?
00:24technomancyhehe; macroshka. love it =)
00:24coventrytechnomancy: Thanks. No, haven't heard of guzheng.
00:25technomancymight be overkill for this
00:26danielglauserTroncle looks nice. Highlight and watch local values
00:27coventryOn a brief glance, it looks like guzheng's code walking doesn't account for the possibility of local bindings shadowing macro names (the main reason for macroshka.)
00:28m0smiththanks all, night
00:29coventryriddley.walk takes a similar approach to guzheng, but deals with this possibility.
00:31coventryKevin Neaton suggested I could use macroshka for a coverage tool at the conj. I think it would be pretty easy to drop it in to something like guzheng or cloverage.
00:32coventry*poof*