mirror of
https://github.com/jerryscript-project/jerryscript.git
synced 2025-12-15 16:29:21 +00:00
e66bb5591d
`Object.prototype.__proto__` has been implemented by most JS engines to give R/W access to prototype chains, well before it made it into the standard. JerryScript has decided not to implement it, exactly because it was not part of ES 5.1. The only fully ES5.1-compatible way of accessing the prototype chain is `Object.getPrototypeOf` for reading. However, ES2015 defines `Object.setPrototypeOf` for rewriting the prototype chain, and JerryScript has now an ES2015 subset profile. So, this commit adds its implementation to JerryScript. Note, this commit does _not_ add `Object.prototype.__proto__`, since that is in the Annex B of ES2015 specification, which is optional for non-web-browser hosts. JerryScript-DCO-1.0-Signed-off-by: Akos Kiss akiss@inf.u-szeged.hu
About profile files
Specify compile definitions in profile files to use when compiling the jerry-core target.
The default profile is es5.1 which disables the ArrayBuffer built-in.
Using profiles with the build system
You can specify the profile for the build system in the following ways:
- with absolute path
- with a name (this options selects profiles/$(name).profile file)
Restrictions
Only single line options are allowed in the profile file. Any line starting with hash-mark is ignored. Semicolon character is not allowed.
Example usage:
1. Using the build script
# assuming you are in jerryscript folder
./tools/build.py --profile=/absolute/path/to/my_profile.any_extension
or
# assuming you are in jerryscript folder
./tools/build.py --profile=minimal
This command selects the profile/minimal.profile file.
2. Using only CMake build system
Set FEATURE_PROFILE option to one of the following values:
- the profile with absolute path
- name of the profile (which needs to exist in the
profilesfolder)