1. 28 Aug, 2014 1 commit
  2. 23 May, 2014 3 commits
    • Nikolai Kosjar's avatar
      C++: Add utf16 indices to Macro and Document::MacroUse · c6358e5d
      Nikolai Kosjar authored
      
      
      In most cases we need to work with the utf16 indices. Only in
      cppfindreferences the byte interface is still needed since there we read
      in files and work on a QByteArray to save memory.
      
      Change-Id: I6ef6a93fc1875a8c9a305c075d51a9ca034c41bb
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      c6358e5d
    • Nikolai Kosjar's avatar
      C++: TranslationUnit::getPosition takes utf16char offsets · 587eb49c
      Nikolai Kosjar authored
      
      
      ...and not byte offsets anymore. This is necessary in order to calculate
      the line and column numbers correctly with respect to unicode code
      points.
      
      Change-Id: I5d79857b3eaefeb8d563b4f1e3938a64debc5e08
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      587eb49c
    • Nikolai Kosjar's avatar
      C++: Support for UTF-8 in the lexer · 70122b30
      Nikolai Kosjar authored
      
      
      This will save us toLatin1() conversations in CppTools (which already
      holds UTF-8 encoded QByteArrays) and thus loss of information (see
      QTCREATORBUG-7356). It also gives us support for non-latin1 identifiers.
      
      API-wise the following functions are added to Token. In follow-up
      patches these will become handy in combination with QStrings.
          utf16chars() - aequivalent of bytes()
          utf16charsBegin() - aequivalent of bytesBegin()
          utf16charsEnd() - aequivalent of bytesEnd()
      
      Next steps:
       * Adapt functions from TranslationUnit. They should work with utf16
         chars in order to calculate lines and columns correctly also for
         UTF-8 multi-byte code points.
       * Adapt the higher level clients:
          * Cpp{Tools,Editor} should expect UTF-8 encoded Literals.
          * Cpp{Tools,Editor}: When dealing with identifiers on the
            QString/QTextDocument layer, code points
            represendet by two QChars need to be respected, too.
       * Ensure Macro::offsets() and Document::MacroUse::{begin,end}() report
         offsets usable in CppEditor/CppTools.
      
      Addresses QTCREATORBUG-7356.
      
      Change-Id: I0791b5236be8215d24fb8e38a1f7cb0d279454c0
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      70122b30
  3. 15 May, 2014 3 commits
  4. 05 Feb, 2014 1 commit
  5. 04 Feb, 2014 1 commit
  6. 21 Jan, 2014 1 commit
  7. 20 Jan, 2014 2 commits
  8. 27 Nov, 2013 1 commit
  9. 15 Oct, 2013 1 commit
  10. 07 Oct, 2013 1 commit
  11. 13 May, 2013 1 commit
  12. 18 Apr, 2013 1 commit
  13. 12 Mar, 2013 1 commit
  14. 19 Feb, 2013 1 commit
  15. 23 Aug, 2012 1 commit
    • Leandro Melo's avatar
      C++: Introduce C++11 raw string literals · e148d030
      Leandro Melo authored
      
      
      Although they are now supported by the lexer
      and parser, it is worth to remind that we still
      need to address an issue concerning the highlight
      of multiline literals (which with the advent of
      the new raw strings will become more common).
      
      Task-number: QTCREATORBUG-6722
      Change-Id: I137337a9ac0152a1f8b9faded0b960c6fe3dd38a
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      e148d030
  16. 17 Aug, 2012 2 commits
  17. 08 Jun, 2012 1 commit
  18. 06 Jun, 2012 1 commit
    • Leandro Melo's avatar
      C++: Introduce unicode char/strings support · 23c637c4
      Leandro Melo authored
      
      
      Those are the types char16_t and char32_t along with the new
      char/string literals u'', U'', u"", u8"", and U"".
      
      This is particularly important for the use of QStringLiteral
      since in some platforms it relies on expansion such as above.
      
      Note: The string literals quickfixes still need some tunning.
      
      Task-number: QTCREATORBUG-7449
      Change-Id: Iebcfea15677dc8e0ebb6143def89a5477e1be7d4
      Reviewed-by: default avatarhjk <qthjk@ovi.com>
      23c637c4
  19. 03 Feb, 2012 1 commit
  20. 01 Feb, 2012 1 commit
  21. 02 Sep, 2011 1 commit
  22. 16 May, 2011 2 commits
  23. 06 May, 2011 1 commit
  24. 13 Apr, 2011 1 commit
  25. 12 Jan, 2011 2 commits
  26. 17 Dec, 2010 1 commit
  27. 11 Aug, 2010 1 commit
  28. 24 Mar, 2010 1 commit
  29. 05 Mar, 2010 1 commit
  30. 15 Feb, 2010 2 commits
  31. 10 Feb, 2010 1 commit
    • Erik Verbruggen's avatar
      Fixed pre-precessor bug. · 9806b1e1
      Erik Verbruggen authored
      When a PP line ended with a \ (join line) and the next line was empty
      (ending th joining), the following token would be incorrectly marked as
      joined.
      
      Done-with: Roberto Raggi
      9806b1e1