1. 04 Jun, 2015 1 commit
  2. 18 May, 2015 1 commit
  3. 21 Apr, 2015 1 commit
  4. 09 Mar, 2015 1 commit
  5. 20 Feb, 2015 1 commit
  6. 13 Feb, 2015 1 commit
  7. 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
  8. 04 Aug, 2014 1 commit
  9. 10 Jul, 2014 1 commit
  10. 20 Jun, 2014 1 commit
  11. 03 Jun, 2014 1 commit
  12. 09 May, 2014 1 commit
  13. 05 May, 2014 1 commit
  14. 29 Apr, 2014 1 commit
  15. 14 Apr, 2014 1 commit
  16. 01 Apr, 2014 1 commit
  17. 13 Mar, 2014 2 commits
  18. 11 Mar, 2014 1 commit
  19. 25 Feb, 2014 1 commit
  20. 28 Feb, 2013 1 commit
  21. 12 Mar, 2012 1 commit
  22. 24 Nov, 2011 1 commit
    • keuchel@chromium.org's avatar
      Introduce extended mode. · 1e9a7267
      keuchel@chromium.org authored
      This CL introduces a third mode next to the non-strict
      (henceforth called 'classic mode') and 'strict mode'
      which is called 'extended mode' as in the current
      ES.next specification drafts. The extended mode is based on
      the 'strict mode' and adds new functionality to it. This
      means that most of the semantics of these two modes
      coincide.
      
      The 'extended mode' is entered instead of the 'strict mode'
      during parsing when using the 'strict mode' directive
      "use strict" and when the the harmony-scoping flag is
      active. This should be changed once it is fully specified how the 'extended mode' is entered.
      
      This change introduces a new 3 valued enum LanguageMode
      (see globals.h) corresponding to the modes which is mostly
      used by the frontend code. This includes the following
      components:
      * (Pre)Parser
      * Compiler
      * SharedFunctionInfo, Scope and ScopeInfo
      * runtime functions: StoreContextSlot,
        ResolvePossiblyDirectEval, InitializeVarGlobal,
        DeclareGlobals
      
      The old enum StrictModeFlag is still used in the backend
      when the distinction between the 'strict mode' and the 'extended mode' does not matter. This includes:
      * SetProperty runtime function, Delete builtin
      * StoreIC and KeyedStoreIC
      * StubCache
      
      Review URL: http://codereview.chromium.org/8417035
      
      git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@10062 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
      1e9a7267
  23. 27 Oct, 2011 1 commit
  24. 09 Jun, 2011 1 commit
  25. 06 May, 2011 2 commits
  26. 03 May, 2011 1 commit
  27. 18 Jan, 2011 1 commit
  28. 22 Dec, 2010 1 commit
  29. 23 Nov, 2010 1 commit