|
From: Waylan L. <wa...@gm...> - 2008-03-06 02:37:24
|
On Wed, Mar 5, 2008 at 5:49 PM, Malthe Borch <mb...@gm...> wrote: > > I can see that there is no test suite included with the markdown > package; if believe that it would beneficial to move these debugging > statements out of the package and into a test suite (where you get to > explicitly define what you expect to see in those statements). First, IIRC the debug statements are only in the wrapper functions. I would think that this is the most likely that people using markdown would want to debug. In debugging their app which uses markdown, they might be unsure that their app is actually passing things on to markdown correctly. Those debug messages allow them to easily check that. I think that adds enough value to leave them. > > This way, you can let people know why you're interested in the output > and what you expect to see. > > By the way: I'm only starting this thread because the markdown package > is great work and I'm a happy user :-) Glad to hear it, and glad you brought it up. The testing framework is actually what I want to focus on now that 1.7 it out of the door. I had started to develop some regression tests for the api, but unfortunately lost them in a hard drive failure (and no I didn't have a proper backup). I guess it's back to the drawing board on that. Any input others may have is more than welcome. > > \malthe > To be -- ---- Waylan Limberg wa...@gm... |