<div dir="ltr"><div dir="ltr">On Wed, Nov 13, 2019 at 1:28 PM Billy O'Neal (VC LIBS) <<a href="mailto:bion@microsoft.com">bion@microsoft.com</a>> wrote:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
><span style="color:rgb(32,31,30);font-size:15px;background-color:rgb(255,255,255);display:inline">Will
you be hesitant to update the reference to the grapheme breaking algorithm if it changes in future Unicode standards as well?</span></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Yes. There's a reason why, for example, Java doesn't follow Unicode's rules in its regex implementation, because it would be a breaking change to do that.</div></div></blockquote><div><br></div><div>IMO, this is the wrong way to think about stability w.r.t Unicode. The changes that happen to Unicode are bug fixes. If they change the results users get when they use a certain API, it's a fix, not a regression. Adding an 8-width (or whatever it turns out to be) entry in the table for U+FDFD in a later standard falls into that category.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
><span style="color:rgb(32,31,30);font-size:15px;background-color:rgb(255,255,255);display:inline">It
is important to remember that width estimation is orthogonal to memory safety; format_to_n() is there to give you the memory safety part, and that will never be impacted by the width estimation piece.</span></div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
I agree, but the same is true of sprintf vs. snprintf.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Billy3</div></div></blockquote><div><br></div><div>That sounds right to me, but I don't get the implication. Why did you bring it up?</div><div><br></div><div>Zach</div><div><br></div></div></div>