1. 13 Sep, 2013 1 commit
  2. 10 Sep, 2013 2 commits
    • Erik Verbruggen's avatar
      C++: unify highlighting/code-completion support "factories". · 3a5d3a2f
      Erik Verbruggen authored
      Both semantic highlighting and code-completion go hand-in-hand, so now
      the ModelManagerSupport class acts as a "factory" for the model manager.
      Depending on the mime-type of the document in the editor, the model
      manager will return the appropriate highlighter or code-completion
      engine. If none is registered, the built-in fall-back is used.
      Change-Id: I3e5dbb0e3b58e077dd5eda9aecb2ce5d448ac0b8
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@digia.com>
    • Erik Verbruggen's avatar
      C++: add fallback project part querying · 87a3aac1
      Erik Verbruggen authored
      When a file is not part of any other project part, this project part can
      be used to get at least some compiler flags, defines, etc. to use. This
      can happen when either a file outside a project is opened, or when the
      project description is incomplete.
      Change-Id: I5d595fae7195e8b61dbad14368b6cae9eb15c21b
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@digia.com>
  3. 09 Sep, 2013 2 commits
  4. 19 Aug, 2013 1 commit
  5. 14 Aug, 2013 1 commit
  6. 13 Aug, 2013 1 commit
    • Nikolai Kosjar's avatar
      CppTools: Rework handling of ProjectInfo changes · 8ea14767
      Nikolai Kosjar authored
      (a) The code model manager figures out by itself which files were added
          or removed from the project.
          If this was done successfully, check also the timestamp of the
          common files and reindex if necessary.
      (b) A full reindexing is only triggered if the project configuration
          changes (defines, includes, framework paths).
      (c) If project files were removed, the garbage collector is called.
      Task-number: QTCREATORBUG-9730
      Change-Id: Ib855614b070880576233a3525813617c967a72f3
      Reviewed-by: default avatarFawzi Mohamed <fawzi.mohamed@digia.com>
  7. 08 Aug, 2013 2 commits
  8. 31 Jul, 2013 1 commit
  9. 22 Jul, 2013 1 commit
  10. 24 Jun, 2013 1 commit
  11. 11 Jun, 2013 1 commit
  12. 24 May, 2013 1 commit
  13. 26 Apr, 2013 3 commits
  14. 22 Apr, 2013 1 commit
  15. 10 Apr, 2013 2 commits
  16. 09 Apr, 2013 1 commit
  17. 08 Apr, 2013 1 commit
  18. 03 Apr, 2013 1 commit
  19. 21 Mar, 2013 1 commit
  20. 08 Mar, 2013 1 commit
  21. 27 Feb, 2013 1 commit
  22. 19 Feb, 2013 1 commit
  23. 30 Jan, 2013 1 commit
  24. 29 Jan, 2013 1 commit
  25. 18 Jan, 2013 1 commit
    • Erik Verbruggen's avatar
      C++: add include-guard tracking. · dada2614
      Erik Verbruggen authored
      Track the typical #ifndef/#define/#endif usage in header files to see if
      the macro is an include guard. If so, store it in the Document. No
      behavioural change, just recording the name.
      This can be used in the future to track if a file needs to be re-parsed
      when a macro changes: if it was used in the file, and not defined in it
      nor being the include-guard, a file should be re-preprocessed and
      It can also be used to check if two files have the same include guard.
      Change-Id: I2715f529997a7b24a11bdbc6150652e2669f1a46
      Reviewed-by: default avatarNikolai Kosjar <nikolai.kosjar@digia.com>
  26. 20 Dec, 2012 1 commit
  27. 26 Nov, 2012 1 commit
  28. 06 Nov, 2012 1 commit
  29. 23 Oct, 2012 1 commit
  30. 16 Oct, 2012 1 commit
  31. 05 Oct, 2012 1 commit
  32. 07 Sep, 2012 1 commit
  33. 19 Jul, 2012 1 commit
  34. 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
      - 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>