<br>
<br><br><div class="gmail_quote">On Fri, Aug 21, 2009 at 12:25 PM, Juan Lang <span dir="ltr"><<a href="mailto:juan.lang@gmail.com">juan.lang@gmail.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 class="im">> As I understand from Wine's policies, functions should only be implemented<br>
> if an application requires them. If that's correct, a random search for<br>
> stubs isn't a good idea, because the follow up question would be "which<br>
> application requires this function?".<br>
<br>
</div>We certainly prioritize functions that an application needs, but we<br>
don't prohibit code that doesn't identify an application that needs<br>
it. It's true that we often ask on this mailing list which<br>
application needs a function, but I think that's generally when a<br>
patch looks strange for some other reason. One of the usual reasons<br>
is that it's lacking a test.<br>
<br>
So, going back to the original advice: if you can write good test<br>
cases for a function, then there's a decent chance you can implement<br>
it, and both tests and the implementation can find their way into<br>
Wine. If you can't write good test cases, you'll have a much harder<br>
time getting your code into Wine.<br>
<font color="#888888">--Juan<br>
</font></blockquote></div><br>Thanks for the clarification.<br><br clear="all"><br>--Stephen<br><br>programmer, n:<br> A red eyed, mumbling mammal capable of conversing with inanimate monsters.<br><br>