2008/8/14 Aldy Hernandez <[EMAIL PROTECTED]>: >> There are various issues that would need to be addressed to have >> decent caret diagnostics: > > Agreed. I think having caret diagnostics in place is a good first step, > if only because it'll make debugging of column diagnostics easier. > After this, we can modify the testsuite machinery to test column > accuracy, and have a suite of tests to work from. I'm not sure whether > it's best to teach testsuite/lib/*.exp about carets, or just test for > :columns:. > > Anyway, I think it'll be useful to clean up whatever needs cleaning in > your patch, test it, and formally submit it. Do you need help testing > it? What remains to be done?
Memory/Compilation time tests. I don't have the framework to test that and it seems the setup is fairly complicated. So that would be really appreciated. > FWIW, I agree with Joseph that -Wcaret would be better than a configure > option. There is -f[no-]diagnostics-show-caret (-W* options are for controlling warnings, we should not use them for anything else). Cheers, Manuel.
