2008/8/14 Mark Mitchell <[EMAIL PROTECTED]>: > Manuel López-Ibáñez wrote: > >> My proposal is to enable this while not in release mode (like we >> enable checks and dump statistics and output from the optimizers), so >> developers notice wrong locations and open a PR and maybe even fix >> them. > > Manuel -- > > We can all work together, but the approach of "break the compiler and hope > that other developers will fix it" is not a good plan. As Joseph says, this > needs to be configured off by default (for compatibility with the way GCC > has worked since forever, and for compatibility with the GNU standards), and > there needs to be an option to turn it on. You will need to recruit others > who are willing to invest in helping to improve the new mode's quality.
The locations are as wrong now as they will be after enabling caret diagnostics. The only difference is that no one pays attention right now because that would require to enable -fshow-column and count column numbers. So I am certainly not "breaking the compiler and hoping that other developers will fix it". This is *exactly* like printing statistics at the end of the compilation. It may hint you that something is broken somewhere but you can freely ignore it as a visual hassle of the experimental compiler. BTW, all those time/memory statistics didn't break anything when they were added? And they are given even if no error/warning is printed. Cheers, Manuel.
