lukechilds/node - node - Gitea: Git with a cup of tea

8872 Commits

131 Branches

446 Tags

325 MiB

Tree: 3c6b5d5df1

Commit Graph

Author	SHA1	Message	Date
Ben Noordhuis	110a9cd8db	lib, src: upgrade after v8 api change This is a big commit that touches just about every file in the src/ directory. The V8 API has changed in significant ways. The most important changes are: * Binding functions take a const v8::FunctionCallbackInfo<T>& argument rather than a const v8::Arguments& argument. * Binding functions return void rather than v8::Handle<v8::Value>. The return value is returned with the args.GetReturnValue().Set() family of functions. * v8::Persistent<T> no longer derives from v8::Handle<T> and no longer allows you to directly dereference the object that the persistent handle points to. This means that the common pattern of caching oft-used JS values in a persistent handle no longer quite works, you first need to reconstruct a v8::Local<T> from the persistent handle with the Local<T>::New(isolate, persistent) factory method. A handful of (internal) convenience classes and functions have been added to make dealing with the new API a little easier. The most visible one is node::Cached<T>, which wraps a v8::Persistent<T> with some template sugar. It can hold arbitrary types but so far it's exclusively used for v8::Strings (which was by far the most commonly cached handle type.)	11 years ago
Timothy J Fontaine	c0281f1b30	build: fix include order for building on windows fallout from the tls_wrap feature landing	12 years ago
Fedor Indutny	6978e998ee	process: abstract out HandleToStream Originally contributed by @tjfontaine, but modified to be faster and more generic.	12 years ago

Author

SHA1

Message

Date

Ben Noordhuis

110a9cd8db

lib, src: upgrade after v8 api change

This is a big commit that touches just about every file in the src/
directory. The V8 API has changed in significant ways. The most
important changes are:

* Binding functions take a const v8::FunctionCallbackInfo<T>& argument
  rather than a const v8::Arguments& argument.

* Binding functions return void rather than v8::Handle<v8::Value>. The
  return value is returned with the args.GetReturnValue().Set() family
  of functions.

* v8::Persistent<T> no longer derives from v8::Handle<T> and no longer
  allows you to directly dereference the object that the persistent
  handle points to. This means that the common pattern of caching
  oft-used JS values in a persistent handle no longer quite works,
  you first need to reconstruct a v8::Local<T> from the persistent
  handle with the Local<T>::New(isolate, persistent) factory method.

A handful of (internal) convenience classes and functions have been
added to make dealing with the new API a little easier.

The most visible one is node::Cached<T>, which wraps a v8::Persistent<T>
with some template sugar. It can hold arbitrary types but so far it's
exclusively used for v8::Strings (which was by far the most commonly
cached handle type.)

11 years ago

Timothy J Fontaine

c0281f1b30

build: fix include order for building on windows

fallout from the tls_wrap feature landing

12 years ago

Fedor Indutny

6978e998ee

process: abstract out HandleToStream

Originally contributed by @tjfontaine, but modified to be faster and
more generic.

12 years ago

3 Commits (3c6b5d5df1e445d080737e435675e11b102f0126)