1. 03 Jan, 2014 1 commit
  2. 28 Dec, 2013 1 commit
  3. 11 Dec, 2013 2 commits
  4. 27 Nov, 2013 1 commit
  5. 26 Nov, 2013 1 commit
  6. 18 Nov, 2013 1 commit
  7. 12 Nov, 2013 1 commit
  8. 31 Oct, 2013 1 commit
  9. 23 Oct, 2013 1 commit
    • Nikolai Kosjar's avatar
      C++: Safe accessing of elements of TranslationUnit::_tokens · 1a5c7d8e
      Nikolai Kosjar authored
      
      
      Until now std::vector::at() was used to access the elements. This is
      handy for debugging since an exception is thrown for invalid indices,
      but it does not stop Qt Creator from crashing because exceptions are not
      caught.
      
      This is especially a problem for the parser, which has to look ahead via
      LA(n), which accesses TranslationUnit::_tokens.
      
      With this patch, explicit bounds checking is done before accessing the
      elements and thus calls to
      
        std::vector::at() // bounds checking, throwing out_of_range
      
      were replaced by calls to
      
        std::vector::operator[]() // no bounds checking, not throwing out_of_range
      
      Measuring the parse time for the Qt Creator project shows that there is
      no slowdown. In both cases, with and without the patch, about 15s are
      needed on the authors machine.
      
      Task-number: QTCREATORBUG-10453
      
      Change-Id: I32b12a526ff7199bcadfc21a3deb5354063a3e3b
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      1a5c7d8e
  10. 15 Oct, 2013 1 commit
  11. 10 Oct, 2013 1 commit
  12. 09 Oct, 2013 1 commit
  13. 07 Oct, 2013 1 commit
  14. 27 Sep, 2013 1 commit
  15. 20 Sep, 2013 1 commit
    • Orgad Shaneh's avatar
      Mute MSVC safety warnings · 5dc58306
      Orgad Shaneh authored
      
      
      Botan:
      C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\xutility:2227:
      warning: C4996: 'std::_Copy_impl': Function call with parameters that may be
      unsafe - this call relies on the caller to check that the passed values are
      correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See
      documentation on how to use Visual C++ 'Checked Iterators'
      
      c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\xutility:2212:
      see declaration of 'std::_Copy_impl'
      
      D:\dev\qt-creator\src\libs\3rdparty\botan\botan.cpp:7248: see reference
      to function template instantiation
      '_OutIt std::copy<const Botan::u32bit*,T*>(_InIt,_InIt,_OutIt)' being compiled
      with
      [
          _OutIt=Botan::word *,
          T=Botan::word,
          _InIt=const Botan::u32bit *
      ]
      
      CppTools:
      C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\include\xutility:2873:
      warning: C4996: 'std::_Mismatch1': Function call with parameters that may be
      unsafe - this call relies on the caller to check that the passed values are
      correct. To disable this warning, use -D_SCL_SECURE_NO_WARNINGS. See
      documentation on how to use Visual C++ 'Checked Iterators'
      
      C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\xutility:2856:
      see declaration of 'std::_Mismatch1'
      
      D:\dev\qt-creator\src\plugins\cpptools\symbolfinder.cpp:388: see reference to
      function template instantiation 'std::pair<_Ty1,_Ty2>
      std::mismatch<QString::const_iterator,QString::const_iterator>(_InIt1,_InIt1,_InIt2)'
      being compiled
      with
      [
          _Ty1=QString::const_iterator,
          _Ty2=QString::const_iterator,
          _InIt1=QString::const_iterator,
          _InIt2=QString::const_iterator
      ]
      
      Change-Id: I09a477e755c4555101b064271f10c08a69576e33
      Reviewed-by: default avatarChristian Kandeler <christian.kandeler@digia.com>
      Reviewed-by: default avatarDavid Schulz <david.schulz@digia.com>
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@digia.com>
      5dc58306
  16. 13 Sep, 2013 1 commit
  17. 12 Sep, 2013 1 commit
  18. 09 Sep, 2013 1 commit
  19. 02 Sep, 2013 1 commit
    • Christian Kandeler's avatar
      Remove superfluous include paths from project files. · 72d17382
      Christian Kandeler authored
      
      
      A lot of our build system files specify unneeded include
      paths. These roughly fall into the following categories:
          a) Paths that are already set in more general files
             such as qtcreator.pri.
          b) Paths that serve no purpose at all, possibly
             left over from earlier versions of the project.
          c) Paths that act as workarounds for wrong include
             statements of the form '#include "xyz.h"', where
             xyz.h is not in the same directory as the including
            file.
      This patch removes such path specifications and fixes the offending
      include statements from case c).
      Tested on Linux, Windows and OSX with qmake and qbs.
      
      Change-Id: I039a8449f8a65df0d616b4c08081145c18ae4b15
      Reviewed-by: default avatarOswald Buddenhagen <oswald.buddenhagen@digia.com>
      Reviewed-by: default avatarJoerg Bornemann <joerg.bornemann@digia.com>
      72d17382
  20. 21 Aug, 2013 1 commit
  21. 31 Jul, 2013 1 commit
  22. 19 Jul, 2013 1 commit
  23. 16 Jul, 2013 1 commit
  24. 15 Jul, 2013 1 commit
  25. 12 Jul, 2013 1 commit
  26. 09 Jul, 2013 1 commit
  27. 06 Jun, 2013 1 commit
  28. 13 May, 2013 1 commit
  29. 10 May, 2013 1 commit
  30. 19 Apr, 2013 1 commit
  31. 18 Apr, 2013 3 commits
  32. 17 Apr, 2013 1 commit
  33. 16 Apr, 2013 1 commit
  34. 15 Apr, 2013 3 commits
  35. 09 Apr, 2013 1 commit