I have to concur with Jim's point -- writing & maintaining the gdb testsuite 
for years, which was based on commands & expected output like these lit tests, 
was a huge drag on everyone's productivity as the debugger changed over time.  
This style of test looks wonderfully easy to read & write & debug, but that's 
only if you ignore long-term maintainability, then you quickly find that it was 
a huge mistake.  I have nothing against lit, this is a very nice way of writing 
commands & expected output tests, but having lived through the consequences of 
that style testsuite, I couldn't imagine making that choice again, especially 
when we've avoided it so far.  It's a bit more work to read & write & debug the 
SB API testsuites that we have today, but it's vastly more maintainable 
long-term.
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to