<br><br><div class="gmail_quote">On Mon, Sep 28, 2009 at 3:02 PM, Levente Uzonyi <span dir="ltr"><<a href="mailto:leves@elte.hu">leves@elte.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi!<div class="im"><br>
<br>
On Mon, 28 Sep 2009, Michael van der Gulik wrote:<br>
<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
On Mon, Sep 28, 2009 at 1:38 PM, <<a href="mailto:commits@source.squeak.org" target="_blank">commits@source.squeak.org</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Item was added:<br>
+ ----- Method: BlockClosure>>timeToRunWithoutGC (in category 'evaluating')<br>
</blockquote>
<br></div><div class="im">
Could this method be put somewhere other than in Kernel, say for example in<br>
a separate profiling package?<br>
<br>
</div></blockquote>
<br>
Since #timeToRun is in the Kernel package and it's a profiling method, it seemed obvious to use the same package and category for this method. Any reason why it should be in another package (if it will get into the trunk)?<br>
<br></blockquote><div><br>My style would be to have the kernel only contain kernel stuff, and a separate profiling package would contain profiling stuff including >>timeToRun. Ordinary users don't need profiling tools. It's subjective though; either way would work.<br>
</div></div><br>Gulik.<br clear="all"><br>-- <br><a href="http://gulik.pbwiki.com/">http://gulik.pbwiki.com/</a><br>