1. 19 Oct, 2012 1 commit
  2. 15 Oct, 2012 3 commits
  3. 11 Oct, 2012 1 commit
  4. 10 Oct, 2012 1 commit
  5. 08 Oct, 2012 1 commit
    • Andre Hartmann's avatar
      Fix encoding of non-opened include files. · 82d312aa
      Andre Hartmann authored
      
      
      The old implementation readed the file and converted the QString toUtf8,
      which seems wrong. Now use Creators default encoding.
      
      This fixes at least wrong macro offsets that leaded to highlighting
      errors in Find Usages, if there were non-ASCII characters before the
      macro definition.
      
      This should also partially solve QTCREATORBUG-7122.
      
      Change-Id: Ic4a5add5f4769bd3d5b62fc2d67598e7abf352d9
      Reviewed-by: default avatarErik Verbruggen <erik.verbruggen@digia.com>
      82d312aa
  6. 05 Oct, 2012 2 commits
  7. 02 Oct, 2012 1 commit
  8. 28 Sep, 2012 1 commit
    • Przemyslaw Gorszkowski's avatar
      Fix crashes when typing code · 7e9913f0
      Przemyslaw Gorszkowski authored
      
      
      Problem was with cyclic recurrence.
      To solve it we need to check if derived class is different class than its base class.
      Keep completion corrected.
      Include some unit tests when base class has the same name as derived.
      
      Task-number: QTCREATORBUG-7887
      Change-Id: I7973c0b06e3b62d2da3d06048f4327d18a0b8011
      Reviewed-by: default avatarhjk <qthjk@ovi.com>
      7e9913f0
  9. 13 Sep, 2012 1 commit
  10. 12 Sep, 2012 1 commit
  11. 07 Sep, 2012 1 commit
  12. 29 Aug, 2012 1 commit
  13. 23 Aug, 2012 2 commits
  14. 17 Aug, 2012 1 commit
  15. 09 Aug, 2012 1 commit
  16. 06 Aug, 2012 2 commits
  17. 30 Jul, 2012 2 commits
  18. 23 Jul, 2012 1 commit
  19. 20 Jul, 2012 1 commit
  20. 19 Jul, 2012 1 commit
  21. 17 Jul, 2012 3 commits
    • Leandro Melo's avatar
      C++: Change back highlighting of types · 441c652c
      Leandro Melo authored
      The type highlighting change part of the recent patch
      4a2a17af
      
       didn't seem to
      please much from a visual point of view. It's a better
      idea to keep the type highlighting as it was for now
      and in the future try again the approach with an explicit
      option and perhaps a more restrictive context.
      
      The other patch is not reverted entirely because it does
      fix a couple of bugs.
      
      Change-Id: I806afa3d8c1c4b241080b8704255d737f61ee12c
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      441c652c
    • Leandro Melo's avatar
      C++: Changes in semantic highlighting · 4a2a17af
      Leandro Melo authored
      
      
      - Fix issues with virtual/non-virtual destructors. They were not
        being correctly identified in some cases - in particular on certain
        uses in derived classes.
      
      - Since now we do have a highlighting item for regular functions,
        constructors and destructors are now highlighted as such. This is
        more semantically correct and actually makes navigation and readiblity
        more distinguishable, since it cleary differentiates the type itself
        from its uses in expressions and declarators. (This seems to be what
        other IDEs like Eclipse, Visual Studio, KDevelop are doing.)
      
        NOTE: There's a switch to disable this item in the case it doesn't
        get good acceptance. Actually, the switch can be made a user
        setting...?
      
      - Change the default color scheme so regular and virtual functions
        have the same color (virtuals continue to be italic). This makes
        sense given the above mentioned changes in constructors/destructors
        highlighting behavior. (In other schemes virtual funcions don't have
        different color, so this shouldn't be necessary in those.)
      
      - Small renaming: "members" are now "fields" - consistent, since
        they apply for data and it's the term used in the UI.
      
      Change-Id: Ib1aa9c0bbf28a31d09f5696460b0095fbe29de80
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      4a2a17af
    • Sergey Shambir's avatar
      Added tooltips on completions proposals · edabcb40
      Sergey Shambir authored
      
      
      Change-Id: Ic22b99e25159edfa4977e13c98f334ce75809af7
      Reviewed-by: default avatarOrgad Shaneh <orgads@gmail.com>
      Reviewed-by: default avatarEike Ziller <eike.ziller@nokia.com>
      edabcb40
  22. 29 Jun, 2012 2 commits
  23. 28 Jun, 2012 2 commits
  24. 25 Jun, 2012 1 commit
    • Leandro Melo's avatar
      C++: Core changes in preprocessing · d6ccffc0
      Leandro Melo authored
      
      
      Summary of most relevant items:
      
      - Preprocessor output format change. No more gen true/false. Instead
        a more intuitive and natural expansion (like from a real compiler) is
        performed directly corresponding to the macro invocation. Notice that
        information about the generated tokens is not lost, because it's now
        embedded in the expansion section header (in terms of lines and columns
        as explained in the code). In addition the location on where the macro
        expansion happens is also documented for future use.
      
      - Fix line control directives and associated token line numbers.
        This was not detected in tests cases because some of them were
        actually wrong: Within expansions the line information was being
        considered as originally computed in the macro definition, while
        the desired and expected for Creator's reporting mechanism (just
        like regular compilers) is the line from the expanded version
        of the tokens.
      
      - Do not allow for eager expansion. This was previously being done
        inside define directives. However, it's not allowed and might
        lead to incorrect results, since the argument substitution should
        only happen upon the macro invocation (and following nested ones).
        At least GCC and clang are consistent with that. See test case
        tst_Preprocessor:dont_eagerly_expand for a detailed explanation.
      
      - Revive the 'expanded' token flag. This is used to mark every token
        that originates from a macro expansion. Notice, however, that
        expanded tokens are not necessarily generated tokens (although
        every generated token is a expanded token). Expanded tokens that
        are not generated are those which are still considered by our
        code model features, since they are visible on the editor. The
        translation unit is smart enough to calculate line/column position
        for such tokens based on the information from the expansion section
        header.
      
      - How expansions are tracked has also changed. Now, we simply add
        two surrounding marker tokens to each "top-level" expansion
        sequence. There is an enumeration that control expansion states.
        Also, no "previous" token is kept around.
      
      - Preprocessor client methods suffered a change in signature so
        they now receive the line number of the action in question as
        a paramater. Previously such line could be retrieved by the client
        implementation by accessing the environment line. However, this
        is not reliable because we try to avoid synchronization of the
        output/environment lines in order to avoid unnecessary output,
        while expanding macros or handling preprocessor directives.
      
      - Although macros are not expanded during define directives (as
        mentioned above) the preprocessor client is now "notified"
        when it sees a macro. This is to allow usage tracking.
      
      - Other small stuff.
      
      This is all in one patch because the fixes are a consequence
      of the change in preprocessing control.
      
      Change-Id: I8f4c6e6366f37756ec65d0a93b79f72a3ac4ed50
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      d6ccffc0
  25. 20 Jun, 2012 1 commit
  26. 19 Jun, 2012 2 commits
  27. 06 Jun, 2012 2 commits
    • 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
    • Andre Hartmann's avatar
      Implemented Rename Macro Usages · 44a3a5e0
      Andre Hartmann authored
      
      
      Works the same way as Rename Usages for C++ Symbols.
      
      For now, no Search Again as this requieres further work.
      
      Task-number: QTCREATORBUG-413
      
      Change-Id: I09e85ea1e8c247f5ce0b6bc566aba8018c1569e4
      Reviewed-by: default avatarLeandro Melo <leandro.melo@nokia.com>
      44a3a5e0
  28. 05 Jun, 2012 1 commit