Hello Ahmed, Hi Orgad, Could you please send me any un- or misrecognized error together with information whether it was received on stdout (black text) or stderr (red text) and information on the actual compiler (type, version output, etc.) that produced this output? Bug reports of course work best for this.
Fixing these issues tends to be easy and fast: We do have very good unit-test coverage in this area (I can provide pointers if anybody is willing to help out with this:-). I am constantly on the lookout for misdetected compiler lines... As a rule of thumb there is no documentation as to what compilers will print in error/warning cases (with a few exceptions) and the output tends to vary widely -- even inside on compiler family -- based on target architecture, the version number and phase of the moon:-/ Best Regards, Tobias 2013/4/22 Orgad Shaneh <[email protected]>: > On Mon, Apr 22, 2013 at 4:13 PM, Ahmed Saidi <[email protected]> wrote: >> >> Hi >> >> I'm using Qt Creator from master branch, recently i notice that the Issues >> output pane doesn't show some errors even if they appear in compile output, >> for example: >> int n = 08; >> or >> int n = ; >> >> the line isn't highlighted in the text editor too >> >> am i the only one who have this problem? >> >> _______________________________________________ >> Qt-creator mailing list >> [email protected] >> http://lists.qt-project.org/mailman/listinfo/qt-creator >> > > You're not alone :) > > Had this with gcc both on Windows and Debian. > > - Orgad > > _______________________________________________ > Qt-creator mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/qt-creator > _______________________________________________ Qt-creator mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/qt-creator
