1. 28 Aug, 2019 1 commit
  2. 27 Aug, 2019 2 commits
  3. 26 Aug, 2019 1 commit
  4. 25 Aug, 2019 2 commits
    • rswindell's avatar
      Fix typo in previous commit. Thanks, NotBert. · d114d05b
      rswindell authored
      d114d05b
    • deuce's avatar
      Add js.exec(). · d53cddaf
      deuce authored
      This allows executing a new script in a specified scope, much like load().
      There are important differences however...
      1) js.exec() *must* specify a scope.
      2) js.exec()d scripts can call exit() and their handlers are ran then,
         rather than when the parent script exists as in js.load().
      3) The js object is installed in the scope with the real JS object as the
         prototype.  This generally shouldn't be an issue, but if you're doing
         strange things, stranger things may happen.
      4) As part of #3, the exec_path/exec_dir/exec_file/startup_dir/scope
         properties of the JS object represent the new script, not the calling
         one.
      5) js.exec() only searches in the passed startup dir (if specified) and the
         current js.exec_dir path.  It does not search the load paths or the mods
         directory at all.
      
      This API is also subject to change.
      d53cddaf
  5. 28 Dec, 2018 1 commit
  6. 20 Feb, 2018 2 commits
  7. 26 Sep, 2015 1 commit
  8. 25 Apr, 2015 2 commits
    • deuce's avatar
      Add jsdocs for js.scope. · 18e8e576
      deuce authored
      18e8e576
    • deuce's avatar
      Fix exit() behaviour by introducing the new js.scope value which is the · f3256d81
      deuce authored
      scripts global scope (as opposed to js.global which is the instance global
      scope), and having exit() define exit_code in js.scope instead of js.global.
      
      This also sets exit_code in js.scope to null when preparing to execute a new
      script.  If a new script starts in the same scope as an old one, the old
      exit_code value will be destroyed.
      
      This should only impact scripts where js.global != js.scope (bbs.exec()ed,
      and mailsrvr)
      f3256d81
  9. 08 Oct, 2013 1 commit
  10. 03 Oct, 2013 1 commit
  11. 13 Sep, 2013 1 commit
  12. 16 Mar, 2013 1 commit
  13. 08 Feb, 2013 1 commit
  14. 15 Mar, 2012 4 commits
  15. 12 Nov, 2011 1 commit
  16. 02 Nov, 2011 1 commit
  17. 29 Oct, 2011 1 commit
  18. 28 Oct, 2011 1 commit
  19. 26 Oct, 2011 1 commit
  20. 19 Oct, 2011 1 commit
  21. 16 Oct, 2011 2 commits
  22. 11 Oct, 2011 1 commit
  23. 10 Oct, 2011 1 commit
  24. 09 Oct, 2011 6 commits
  25. 08 Oct, 2011 2 commits
  26. 31 Aug, 2011 1 commit
    • rswindell's avatar
      Eliminate problematic js properties in non-debug builds: · a3c7a535
      rswindell authored
      js.gc_counter, js.gc_last_bytes, js.bytes, and js.max_bytes
      Since these properties rely on internal JS context structure offsets, they're
      not always compatible with replaced (upgraded or downgraded) JS library
      (shared object or DLL) and can cause crashes in some cases. They can be
      useful in some debugging cases, so I'm leaving them in the debug build, but
      use with caution.
      a3c7a535