This repository was archived by the owner on Apr 22, 2023. It is now read-only.
Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository:
nodejs/node-v0.x-archive
base:
master
...
head repository:
polazarus/node
compare:
master
Checking mergeability…
Don’t worry, you can still create the pull request.
- 1 commit
- 5 files changed
- 1 contributor
Commits on Nov 30, 2011
-
V8's internal representation of string is in UCS-2, that is, V8 considers 16-bit code units (from 0x0000 to 0xFFFF). But, Unicode gives sense to codepoints upto U+10FFFF. UTF-16 proposes to code the extra characters (>U+FFFF) as a pair of two 16-bit code units, aka a surrogate pair. V8 does not care for it but do relatively well with it, up to the point you need to actually encode or decode text in the most used Unicode encoding, UTF-8. V8 and consequently Node.js, UTF-8 codec now handles those extra Unicode codepoints. This commit modifies three functions of v8: String::WriteUtf8 (api.cc), String::Utf8Length (objects.cc), and Heap::AllocateStringFromUtf8Slow (heap.cc). It also adds some utility functions to v8 (in unicode.h and unicode-inl.h) about surrogate pairs.
Configuration menuCopy the full SHA7543ab9 View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master