Re: [Pharo-project] [squeak-dev] code coverage

2013-02-22 Thread Marcus Denker
On Feb 22, 2013, at 9:16 AM, Goubier Thierry wrote: > Le 22/02/2013 07:23, Marcus Denker a écrit : >> >> On Feb 21, 2013, at 9:52 PM, Frank Shearar wrote: >> >>> On 21 February 2013 19:52, Eliot Miranda wrote: Hi All, anyone have any bytecode-to-bytecode transformation to

Re: [Pharo-project] [squeak-dev] code coverage

2013-02-22 Thread Goubier Thierry
Le 22/02/2013 07:23, Marcus Denker a écrit : On Feb 21, 2013, at 9:52 PM, Frank Shearar wrote: On 21 February 2013 19:52, Eliot Miranda wrote: Hi All, anyone have any bytecode-to-bytecode transformation tools for doing basic-block resolution coverage? Is it possible that Jejak [1] m

Re: [Pharo-project] [squeak-dev] code coverage

2013-02-22 Thread Goubier Thierry
Le 21/02/2013 21:52, Frank Shearar a écrit : On 21 February 2013 19:52, Eliot Miranda wrote: Hi All, anyone have any bytecode-to-bytecode transformation tools for doing basic-block resolution coverage? Is it possible that Jejak [1] might vaguely fit this bill? It's a tracing tool, but

Re: [Pharo-project] [squeak-dev] code coverage

2013-02-21 Thread Marcus Denker
On Feb 21, 2013, at 9:52 PM, Frank Shearar wrote: > On 21 February 2013 19:52, Eliot Miranda wrote: >> Hi All, >> >> anyone have any bytecode-to-bytecode transformation tools for >> doing basic-block resolution coverage? > > Is it possible that Jejak [1] might vaguely fit this bill? It's

Re: [Pharo-project] [squeak-dev] code coverage

2013-02-21 Thread Frank Shearar
On 21 February 2013 19:52, Eliot Miranda wrote: > Hi All, > > anyone have any bytecode-to-bytecode transformation tools for > doing basic-block resolution coverage? Is it possible that Jejak [1] might vaguely fit this bill? It's a tracing tool, but maybe one could hack something on the side