<br><br><div class="gmail_quote">On Wed, Jul 29, 2009 at 5:16 PM, Phil Thompson <span dir="ltr"><<a href="mailto:phil@riverbankcomputing.com">phil@riverbankcomputing.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
On Wed, 29 Jul 2009 17:11:41 +0200, Arve Knudsen <<a href="mailto:arve.knudsen@gmail.com">arve.knudsen@gmail.com</a>><br>
wrote:<br>
<div class="im">> Phil, can you please confirm whether you will implement any such<br>
debugging<br>
> aids in the SIP API (I take it there is nothing at the moment)? I could<br>
> really use some introspection abilities into SIP when things don't work<br>
as<br>
> expected, as happens from time to time. This should save me a lot of<br>
> frustration ..<br>
<br>
</div>I have no plans to unless you can give me some specific requirements that I<br>
consider reasonable. "Some introspection abilities" is too vague.</blockquote><div><br></div><div>OK. I'm being vague because I don't understand this aspect of SIP very well, from my perspective some magic simply fails to produce the expected result (i.e., it doesn't find a type definition). If I knew more about the process which actually fails, I could also have more of an idea of how to observe this from the outside. I'll see if I can understand more from the SIP source, and then propose something concrete.</div>
<div><br></div><div>Thanks,</div><div>Arve</div></div>