On 03/29/2012 09:41 AM, ext Lincoln Ramsay wrote: > Why can't Creator just set the QT_MESSAGE_PATTERN environment variable > then and leave the default alone? Creator would not need to show the > filename and line number, just use them for when you click on the warnings.
And related to this... If we're going to have warnings that result in click-to-locate then we really need to find a way of doing perl-style carp (ie. warning from the caller's context). I think that both Windows and Glibc have a facility that may allow this to be done but getting something truly cross-platform may not be possible. The QList.at() assertion has always struck me as totally useless because unless you've got a debugger attached you aren't told (and thus cannot find out) _where_ the code that triggered the assertion is. The ability to warn from the caller's perspective would make this assertion so much more useful. -- Lincoln Ramsay - Senior Software Engineer Qt Development Frameworks, Nokia - http://qt.nokia.com/ _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
