So this is helpful in >1% of possible debugging sessions? Wouldn'tthe BasicInspector be sufficient for this?<br><br>Alex<br><br><div class="gmail_quote">On Mon, Mar 22, 2010 at 13:13, David T. Lewis <span dir="ltr"><<a href="mailto:lewis@mail.msen.com">lewis@mail.msen.com</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;"><div><div></div><div class="h5">On Mon, Mar 22, 2010 at 12:55:55PM +0100, Alexander Lazarevi?? wrote:<br>
> On Mon, Mar 22, 2010 at 12:17, Bert Freudenberg <<a href="mailto:bert@freudenbergs.de">bert@freudenbergs.de</a>>wrote:<br>
><br>
> > Also, instance variable order is significant so in a debug method I'd<br>
> > rather prefer to not see it changed - what's your reasoning here?<br>
> ><br>
><br>
> Maybe I just can't see how it does help in a debugger to have the instance<br>
> vars listed in the order they were defined. Usually I'm looking for names<br>
> not slot indices? No?<br>
><br>
> (Truly wondering!)<br>
<br>
</div></div>Usually yes, but not always. See senders of #instVarAt:. If you were<br>
debugging any of those methods, you would want to see the variables<br>
listed in the correct order.<br>
<br>
Dave<br>
<br>
<br>
</blockquote></div><br>