1. 09 Mar, 2015 1 commit
  2. 03 Mar, 2015 1 commit
  3. 26 Feb, 2015 2 commits
    • adamk's avatar
      Re-introduce ImportDeclaration to the parser · fa293dd7
      adamk authored
      This also adds a new VariableMode, IMPORT, which will be
      used to do appropriate binding for Import-declared Variables.
      
      Only named imports are handled for now. "import *" and default
      import syntaxes have had their TODOs adjusted to match the new
      code structure.
      
      BUG=v8:1569
      LOG=n
      
      Review URL: https://codereview.chromium.org/948303004
      
      Cr-Commit-Position: refs/heads/master@{#26895}
      fa293dd7
    • marja's avatar
      [strong] Declaration-after-use errors. · 1eddcf5b
      marja authored
      We cannot yet detect use-before-declaration in general, because for that we'd
      need to analyze the context when compiling. But we can detect an error case
      where we first see a use, then a declaration.
      
      For this, I also added end position tracking (needed for error messages) to
      VariableProxy.
      
      Note: the position naming is completely inconsistent: start_position &
      end_position, position & end_position, pos & end_pos, beg_pos & end_pos, to name
      a few. This doesn't fix all of it, but tries to unify towards start_position &
      end_position whenever possible w/ minimal changes.
      
      BUG=
      
      Review URL: https://codereview.chromium.org/943543002
      
      Cr-Commit-Position: refs/heads/master@{#26880}
      1eddcf5b
  4. 25 Feb, 2015 3 commits
  5. 24 Feb, 2015 1 commit
  6. 20 Feb, 2015 2 commits
  7. 19 Feb, 2015 3 commits
  8. 17 Feb, 2015 2 commits
  9. 13 Feb, 2015 1 commit
  10. 12 Feb, 2015 3 commits
  11. 11 Feb, 2015 1 commit
  12. 10 Feb, 2015 1 commit
    • marja's avatar
      Get rid of PreParserScope. · 0ca9bef3
      marja authored
      It's unnecessary; PreParser can just use normal Scopes for the things it needs
      to track. Note: the only functionalities of PreParserScope were keeping track of
      the scope stack, and for each scope, the scope type and language mode. Those are
      now done by Scope. PreParser doesn't yet put variables into scopes (that will be
      done in a follow up).
      
      R=rossberg@chromium.org
      BUG=
      
      Review URL: https://codereview.chromium.org/912563004
      
      Cr-Commit-Position: refs/heads/master@{#26544}
      0ca9bef3
  13. 06 Feb, 2015 3 commits
  14. 04 Feb, 2015 1 commit
    • marja's avatar
      Introduce LanguageMode, drop StrictMode. · c7851da4
      marja authored
      This enables adding more language modes in the future.
      
      For maximum flexibility, LanguageMode is a bitmask, so we're not restricted to
      use a sequence of language modes which are progressively stricter, but we can
      express the language mode as combination of features.
      
      For now, LanguageMode can only be "sloppy" or "strict", and there are
      STATIC_ASSERTS in places which need to change when more modes are added.
      
      LanguageMode is a bit like the old LanguageMode when "extended" mode was still
      around (see https://codereview.chromium.org/8417035 and
      https://codereview.chromium.org/181543002 ) except that it's transmitted through
      all the layers (there's no StrictModeFlag).
      
      BUG=
      
      Review URL: https://codereview.chromium.org/894683003
      
      Cr-Commit-Position: refs/heads/master@{#26419}
      c7851da4
  15. 03 Feb, 2015 1 commit
  16. 30 Jan, 2015 1 commit
    • adamk's avatar
      Implemented new syntax for ImportDeclarations · 0c928d53
      adamk authored
      Also had to split ParseImportsList and ParseExportClause into separate
      methods as they have different rules about reserved words and arguments/eval.
      
      Added lots more test cases, including some export cases that were missed before
      due to incorrect checking of reserved words.
      
      BUG=v8:1569
      LOG=n
      
      Review URL: https://codereview.chromium.org/887843002
      
      Cr-Commit-Position: refs/heads/master@{#26338}
      0c928d53
  17. 29 Jan, 2015 1 commit
    • aperez's avatar
      Do not create unresolved variables when parsing arrow functions lazily · 91b87e7a
      aperez authored
      Arrow function parameter lists are parsed as expressions. When an identifier
      is found a VariableProxy is created and added to the list of unresolved
      variables for the scope. When parsing a function lazily, the scope has been
      already resolved, so with this patch only the VariableProxy is created,
      without adding it as an unresolved variable in the scope.
      
      BUG=v8:3501
      LOG=Y
      
      Review URL: https://codereview.chromium.org/880253004
      
      Cr-Commit-Position: refs/heads/master@{#26328}
      91b87e7a
  18. 28 Jan, 2015 1 commit
  19. 27 Jan, 2015 1 commit
    • adamk's avatar
      Begin modernization of --harmony-modules · aeb3a717
      adamk authored
      The approach taken in this CL is to incrementally move toward the
      currently-specced version of modules in ES6. The biggest change in this
      patch is separating the parsing of modules from the parsing of scripts,
      getting rid of the 'module' keyword and thus disallowing modules-in-scripts
      as well as modules-in-modules.
      
      The syntax supported by import/export declarations has not yet been significantly
      changed, with the major exception being that import declarations require a string
      as the 'from' part.
      
      Most of the existing tests have been disabled, with a first new test added
      in cctest/test-parsing.
      
      BUG=v8:1569
      LOG=n
      
      Review URL: https://codereview.chromium.org/881623002
      
      Cr-Commit-Position: refs/heads/master@{#26299}
      aeb3a717
  20. 23 Jan, 2015 2 commits
  21. 15 Jan, 2015 2 commits
  22. 12 Jan, 2015 1 commit
  23. 07 Jan, 2015 1 commit
  24. 17 Dec, 2014 2 commits
  25. 16 Dec, 2014 2 commits
    • arv's avatar
      Revert of ES6 computed property names (patchset #1 id:1 of... · 5f22fdd5
      arv authored
      Revert of ES6 computed property names (patchset #1 id:1 of https://codereview.chromium.org/807173002/)
      
      Reason for revert:
      Crashes Win32. It was not flake.
      
      Original issue's description:
      > ES6 computed property names
      >
      > This adds support for computed property names, under the flag
      > --harmony-computed-property-names, for both object literals and
      > classes.
      >
      > This is a revert of the revert, a76419f0 with
      > no changes. I cannot reproduce the issue on Win8.1 or WinXP. Letting the bots
      > try again.
      >
      > BUG=v8:3754
      > LOG=Y
      > TBR=dslomov@chromium.org
      
      TBR=dslomov@chromium.org
      NOTREECHECKS=true
      NOTRY=true
      BUG=v8:3754
      
      Review URL: https://codereview.chromium.org/807033003
      
      Cr-Commit-Position: refs/heads/master@{#25853}
      5f22fdd5
    • arv's avatar
      ES6 computed property names · a235b107
      arv authored
      This adds support for computed property names, under the flag
      --harmony-computed-property-names, for both object literals and
      classes.
      
      This is a revert of the revert, a76419f0 with
      no changes. I cannot reproduce the issue on Win8.1 or WinXP. Letting the bots
      try again.
      
      BUG=v8:3754
      LOG=Y
      TBR=dslomov@chromium.org
      
      Review URL: https://codereview.chromium.org/807173002
      
      Cr-Commit-Position: refs/heads/master@{#25851}
      a235b107