<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Sep 18, 2010, at 10:18 PM, Steve Holden wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; "><blockquote type="cite">I could probably be persuaded to merge the APIs, but the email6<br></blockquote><blockquote type="cite">precedent suggests to me that separating the APIs better reflects the<br></blockquote><blockquote type="cite">mental model we're trying to encourage in programmers manipulating<br></blockquote><blockquote type="cite">text (i.e. the difference between the raw octet sequence and the text<br></blockquote><blockquote type="cite">character sequence/parsed data).<br></blockquote><blockquote type="cite"><br></blockquote>That sounds pretty sane and coherent to me.<br></span></span></blockquote></div><br><div>While I don't like the email6 precedent as such (that there would be different <i>parsed</i> objects, based on whether you started parsing with bytes or with strings), the idea that when you are working <i>directly</i> with bytes or text, you should have to know which one you have, is a good one. +1 for keeping the APIs separate with 'urlsplitb' etc.</div></body></html>