I took chromatic's Runops::Trace and hacked it up so I could do code
coverage. I can now tell which code path is triggered by which inputs.
Check this badness out. The punchline is the lists of equivalent
inputs. Roughly. Ops can return different things and I'm not paying
attention to the inputs
Josh,
I'm not sure that I understand this message (probably because I'm not
a perl guts hacker), but I am intrigued by your enthusiasm. I
downloaded and read the Runops::Trace code -- it's always a little
surprising and interesting to me to see which parts of the Perl
internals are malle
On 6/16/07, Chris Dolan <[EMAIL PROTECTED]> wrote:
Josh,
Josh, can you explain to us in a little more depth what this means?
Are you showing that certain input values follow the same path
through the code?
Yes.
It looks like the full path through the code is
the key to your hash of runs. If
On Jun 17, 2007, at 12:56 AM, Joshua ben Jore wrote:
On 6/16/07, Chris Dolan <[EMAIL PROTECTED]> wrote:
Josh,
Josh, can you explain to us in a little more depth what this means?
Are you showing that certain input values follow the same path
through the code?
Yes.
It looks like the full pat
On 6/16/07, Chris Dolan <[EMAIL PROTECTED]> wrote:
On Jun 17, 2007, at 12:56 AM, Joshua ben Jore wrote:
> On 6/16/07, Chris Dolan <[EMAIL PROTECTED]> wrote:
>> Josh,
>>
>> Josh, can you explain to us in a little more depth what this means?
>> Are you showing that certain input values follow the
