1. 11 Sep, 2013 1 commit
  2. 11 Jun, 2013 1 commit
  3. 09 Apr, 2013 1 commit
  4. 03 Apr, 2013 1 commit
  5. 29 Jan, 2013 1 commit
  6. 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
      re-parsed.
      
      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>
      dada2614
  7. 15 Oct, 2012 1 commit
  8. 05 Oct, 2012 1 commit
  9. 19 Jul, 2012 1 commit
  10. 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
  11. 19 Apr, 2012 3 commits
  12. 29 Mar, 2012 1 commit
    • Erik Verbruggen's avatar
      [C++] Rewrite of the preprocessor. · 60db5736
      Erik Verbruggen authored
      
      
      This rewrite fixes a couple of issues with the pre-processor. It now
      supports:
      - macros in macro bodies
      - stringification of parameters [cpp.stringize]
      - the concatenation operator [cpp.concat]
      - #include MACRO_HERE
      - defined() inside macro bodies used in pp-conditions.
      
      Change-Id: Ifdb78041fb6afadf44f939a4bd66ce2832b8601f
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      60db5736
  13. 15 Feb, 2012 1 commit
  14. 26 Jan, 2012 1 commit
  15. 03 Nov, 2011 1 commit
  16. 06 May, 2011 1 commit
  17. 13 Apr, 2011 1 commit
  18. 04 Feb, 2011 1 commit
  19. 12 Jan, 2011 2 commits
  20. 17 Dec, 2010 1 commit
  21. 28 May, 2010 1 commit
  22. 05 Mar, 2010 1 commit
  23. 07 Oct, 2009 1 commit
    • Roberto Raggi's avatar
      Removed the MacroResolver · 77aa3064
      Roberto Raggi authored
      Unfortunately, the MacroResolver does not scale and we get pretty bad performances when parsing big projects.
      77aa3064
  24. 30 Sep, 2009 2 commits
  25. 25 Sep, 2009 1 commit
    • Christian Kamm's avatar
      Track more macro uses. · 22ed0255
      Christian Kamm authored
      
      
      In particular macros that are only checked for definition or are
      expanded during the evaluation of an #if or #elif directive are now also
      added to the list available through Document::macroUses().
      
      The names of undefined macros that are interesting (because they're used
      in an #ifdef or a defined(...)) are now available through
      Document::undefinedMacroUses().
      Reviewed-by: default avatarRoberto Raggi <roberto.raggi@nokia.com>
      22ed0255
  26. 14 Aug, 2009 1 commit
  27. 01 Jul, 2009 1 commit
  28. 16 Jun, 2009 1 commit
  29. 15 Jun, 2009 1 commit
  30. 03 Jun, 2009 1 commit
  31. 25 Feb, 2009 2 commits
  32. 13 Jan, 2009 2 commits
  33. 16 Dec, 2008 1 commit
  34. 02 Dec, 2008 1 commit