<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 20, 2012 at 2:15 PM, Göran Krampe <span dir="ltr"><<a href="mailto:goran@krampe.se" target="_blank">goran@krampe.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi list and Eliot!<br>
<br>
A quick bug report:<br>
<br>
If I use 2637 on a Pharo-1.4 image (vanilla) and try "3+4" profile-it (in the menu) it seems that vm parameter number 65 has value "false" and the code for profiling don't expect non numeric values there.<br>
</blockquote><div><br></div><div>and FYI, parameter 65 is "VM supports multiple bytecode sets". It's new, and I would like it to stay. So can we modify the profiling code? No code should assume specific values for as-yet-undefined vm parameters. We have to be able to grow.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
regards, Göran<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div><br>
</div></div>