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 ( http://llvm.org/bugs/show_bug.cgi?id=15927), I've found another bug which hasn't been answered to since March ( http://llvm.org/bugs/show_bug.cgi?id=15505). So, the question is: how ready is YAML I/O ready for using in production code? Thanks! And, BTW, YAML I/O is really convenient to use, so thanks for this awesome library! ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130507/8a90a7f3/attachment.html>
Alexander, This is the first I'd heard of that other bug. I've assigned both those to me to investigate. I think you'll need to try using YAML I/O and see if it robust enough for your needs. -Nick On May 7, 2013, at 10:06 AM, Alexander Kornienko <alexfh at google.com> wrote:> 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 (http://llvm.org/bugs/show_bug.cgi?id=15927), I've found another bug which hasn't been answered to since March (http://llvm.org/bugs/show_bug.cgi?id=15505). > > So, the question is: how ready is YAML I/O ready for using in production code? > > Thanks! > > And, BTW, YAML I/O is really convenient to use, so thanks for this awesome library! ;)-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130507/fea4fa42/attachment.html>
Seemingly Similar Threads
- Documentation doesn't get updated
- [LLVMdev] [llvm-commits] PROPOSAL: LLVM_FALLTHROUGH macro for intended fall-throughs between switch cases
- Missing clang-modernize in 3.8 (Debian 8 Jessie)
- [LLVMdev] Python version requirement for LLVM
- [LLVMdev] [llvm-commits] PROPOSAL: LLVM_FALLTHROUGH macro for intended fall-throughs between switch cases