1. 12 Jan, 2016 1 commit
  2. 23 Sep, 2015 1 commit
  3. 17 Feb, 2015 1 commit
    • Adam Strzelecki's avatar
      C++: Basic support for C++11 user-defined literals · 42581129
      Adam Strzelecki authored
      1. Extends lexer so digit or string can be followed by underscore '_' and
         alphanumeric defining literal.
      
      2. Extends parser so it accepts operator"" _abc(...) user-defined literal
         definition.
      
      3. Adds Token::Flags.userDefinedLiteral bool flag field representing if token
         carries user-defined literal.
      
      4. Adds C++11 auto tests case with: 12_km, 0.5_Pa, 'c'_X, "abd"_L, u"xyz"_M
      
      5. All optional suffix scanning methods now return boolean if the suffix was
         found.
      
      6. Adds C++ Lexer tests for user-defined literals with C++11 feature enabled.
      
      This change however does not make QtCreator understand user-defined literal
      semantics, e.g. properly resolve type when applying custom literal operator.
      
      Change-Id: I30e62f025ec9fb11c39261985ea4d772b1a80949
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@theqtcompany.com>
      42581129
  4. 16 Jan, 2015 1 commit
  5. 18 Dec, 2014 1 commit
  6. 07 Nov, 2014 1 commit
  7. 09 Oct, 2014 1 commit
  8. 05 Jun, 2014 1 commit
  9. 23 May, 2014 2 commits
    • Nikolai Kosjar's avatar
      C++/CppTools: Pass UTF-8 encoded source to Lexer · 57ff9929
      Nikolai Kosjar authored
      The Lexer can handle it now.
      
      Task-number: QTCREATORBUG-7356
      Change-Id: I8c4b03a247656e013d44c3cedca4835e133d4036
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      57ff9929
    • 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
  10. 16 May, 2014 1 commit
  11. 04 Feb, 2014 1 commit
  12. 21 Jan, 2014 1 commit
  13. 20 Jan, 2014 2 commits
  14. 08 Jan, 2014 1 commit
  15. 10 Dec, 2013 1 commit
  16. 03 Dec, 2013 1 commit
  17. 27 Nov, 2013 1 commit
  18. 03 Apr, 2013 1 commit
  19. 12 Mar, 2013 2 commits
  20. 04 Mar, 2013 1 commit
  21. 19 Feb, 2013 1 commit