GNOME Bugzilla – Bug 721355
context: Always use JSVERSION_LATEST
Last modified: 2014-01-02 19:37:16 UTC
Upstream wants to remove this API, so let's prepare ourselves for removing it as well...
Created attachment 265179 [details] [review] context: Always use JSVERSION_LATEST And remove the APIs/ability to scan for a JS version to use. Upstream wants to remove this API.
Review of attachment 265179 [details] [review]: ::: gjs/console.cpp @@ -36,3 @@ { "command", 'c', 0, G_OPTION_ARG_STRING, &command, "Program passed in as a string", "COMMAND" }, { "include-path", 'I', 0, G_OPTION_ARG_STRING_ARRAY, &include_path, "Add the directory DIR to the list of directories to search for js files.", "DIR" }, - { "js-version", 0, 0, G_OPTION_ARG_STRING, &js_version, "JavaScript version (e.g. \"default\", \"1.8\"", "JSVERSION" }, I have a minor concern about applications actually passing this flag, but...eh, they probably don't exist. ::: installed-tests/js/testJS1_8.js @@ -2,3 @@ - -// Test SpiderMonkey JS extensions; see -// https://developer.mozilla.org/en/JavaScript/New_in_JavaScript/1.8 Why not keep this test? I mean, sure most of it is tested elsewhere, but if we're saying we support these features we should keep the test.
Attachment 265179 [details] pushed as 3053f0b - context: Always use JSVERSION_LATEST I'm not sure why I removed that test. Added it back before pushing.