<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>Alexander,</div><div><br></div><div>This is the first I'd heard of that other bug. I've assigned both those to me to investigate. </div><div><br></div><div>I think you'll need to try using YAML I/O and see if it robust enough for your needs.</div><div><br></div><div>-Nick</div><br><div><div>On May 7, 2013, at 10:06 AM, Alexander Kornienko <<a href="mailto:alexfh@google.com">alexfh@google.com</a>> wrote:</div><blockquote type="cite"><div style="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;"><div dir="ltr"><div>I've started using YAML I/O in clang-format configuration parser, and stumbled upon a bug with handling empty input string. While filing it (<a href="http://llvm.org/bugs/show_bug.cgi?id=15927">http://llvm.org/bugs/show_bug.cgi?id=15927</a>), I've found another bug which hasn't been answered to since March (<a href="http://llvm.org/bugs/show_bug.cgi?id=15505">http://llvm.org/bugs/show_bug.cgi?id=15505</a>).</div><div><br></div><div>So, the question is: how ready is YAML I/O ready for using in production code?</div><div><br></div><div>Thanks!</div><div><br></div><div>And, BTW, YAML I/O is really convenient to use, so thanks for this awesome library! ;)</div></div></div></blockquote></div><br></body></html>