<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><blockquote type="cite" class="">On Jan 11, 2016, at 8:05 PM, Philippe Hausler <<a href="mailto:phausler@apple.com" class="">phausler@apple.com</a>> wrote:<br class=""></blockquote><div><blockquote type="cite" class=""><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">Cases like this are kinda cagey because you have to keep track of which string is which; is it the foo result string or the bar result string at .0 versus .1? I find myself always favoring struct or inout for clarity/safety.</span></div></blockquote></div><br class=""><div class="">In the case where the original API distinguishes between the two (-fooAndReturnBar:), you can return a named (or partially-named) tuple, like in one my later examples. In this case, the original API doesn’t have this information either, so we can’t translate it into something better (although I don’t believe this pattern is very common, so that helps).</div><div class=""><br class=""></div><div class="">In the more common case where you have something like fooWithBar: you can add a “bar:” label on the second parameter.</div><div class=""><br class=""></div><div class="">Charles</div><div class=""><br class=""></div></body></html>