<html><body><div>OK. I'll resend with the changes suggested.</div><div><br data-mce-bogus="1"></div><div>~Theodore</div><div><br>On Mar 15, 2016, at 07:03 PM, Alexandre Julliard <julliard@winehq.org> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch"><span class="body-text-content">Theodore Dubois <tblodt@icloud.com> writes:<br><br><blockquote type="cite" class="quoted-plain-text">The reason I need the macro is: If I wrote</blockquote><blockquote type="cite" class="quoted-plain-text">ok(getstring_test(whatever)), first the ok macro would call</blockquote><blockquote type="cite" class="quoted-plain-text">winetest_set_location with the current line number, and then it would</blockquote><blockquote type="cite" class="quoted-plain-text">call getstring_test. The ok macros in getstring_test would call</blockquote><blockquote type="cite" class="quoted-plain-text">winetest_set_location and overwrite the location of the actual</blockquote><blockquote type="cite" class="quoted-plain-text">test. Then if getstring_test returns with a failure, the error message</blockquote><blockquote type="cite" class="quoted-plain-text">has the wrong line number. The only way to fix this is to call</blockquote><blockquote type="cite" class="quoted-plain-text">getstring_test on one line and call ok on the next line.</blockquote><br>There's no reason to call ok on the getstring_test result, since<br>getstring_test would have already reported the error. If you want to<br>know which caller triggered it, you can pass a line number or some<br>string description to getstring_test.<br><br>-- <br>Alexandre Julliard<br><a href="mailto:julliard@winehq.org" data-mce-href="mailto:julliard@winehq.org">julliard@winehq.org</a><br></span></div></div></blockquote></div></body></html>