Last Comment Bug 866344 - Remove support for building without ECMAScript Internationalization API
: Remove support for building without ECMAScript Internationalization API
Status: NEW
:
Product: Core
Classification: Components
Component: JavaScript Engine (show other bugs)
: Trunk
: All All
-- normal with 1 vote (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
: Jason Orendorff [:jorendorff]
Mentors:
http://www.ecma-international.org/ecm...
: 1338013 (view as bug list)
Depends on: 853301 864843 866301 866305 1215247 1215252
Blocks: es-intl 943283
  Show dependency treegraph
 
Reported: 2013-04-26 17:15 PDT by Norbert Lindenberg
Modified: 2017-02-13 10:19 PST (History)
5 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description User image Norbert Lindenberg 2013-04-26 17:15:39 PDT
When the ECMAScript Internationalization API is enabled in all main Mozilla products, the ability to build SpiderMonkey without support for ECMA-402 should be removed.

Steps:
- Remove all definitions for --enable-intl-api from mozconfig files.
- Remove the tests for the --enable-intl-api flag from configure.in and js/src/configure.in files, and update the files as if it was always set.
- Remove the tests for the ENABLE_INTL_API variable from js/src/configure.in and js/src/Makefile.in, and update the files as if it was always set.
- Remove the tests for the ENABLE_INTL_API flag from .h and .cpp files in js/src, and remove code that depends on it being undefined or 0.
- Change the return type of InitRuntimeNumberState as indicated by a comment in jsnum.cpp.
- Remove the localeCompare member from JSLocaleCallbacks in jsapi.h, and the code setting it and the Compare function from js/xpconnect/src/XPCLocale.cpp.
- Remove the skip-if(!this.hasOwnProperty("Intl")) conditions from js/src/tests/jstests.list and the tests within js/src/tests/Intl.
Comment 1 User image Henri Sivonen (:hsivonen) 2017-02-13 10:19:24 PST
*** Bug 1338013 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.