[v8-juice] r2254 committed - Edited wiki page V8Convert_FunctionBinding through web user interface.

1 view
Skip to first unread message

v8-j...@googlecode.com

unread,
Jul 11, 2012, 2:02:30 PM7/11/12
to v8-juice-...@googlegroups.com
Revision: 2254
Author: sgb...@gmail.com
Date: Wed Jul 11 11:02:18 2012
Log: Edited wiki page V8Convert_FunctionBinding through web user
interface.
http://code.google.com/p/v8-juice/source/detail?r=2254

Modified:
/wiki/V8Convert_FunctionBinding.wiki

=======================================
--- /wiki/V8Convert_FunctionBinding.wiki Mon Apr 9 00:44:21 2012
+++ /wiki/V8Convert_FunctionBinding.wiki Wed Jul 11 11:02:18 2012
@@ -514,12 +514,12 @@

= Converting Functors to Callbacks =

-We can also bind functors to v8, with the following limitations:
+Interestingly, binding C++ functors to v8 turns out to be a special case
of binding a member method, and the implementation for it is just a thin
wrapper around the member method binding. However, the extra level of
abstraction adds a couple limitations on such bindings. Functors can be
bound to v8 provided they can meet the following requirements:

* They are assumed to be stateless. The library makes no guarantees
about the lifetime of any given functor instance.
- * The must have one or more _const_ `operator()`s.
-
-The can be converted to `v8::InvocationCallback`s like:
+ * The must have one or more _const_ `operator()`s. The `const`
requirement is an unfortunate side-effect of the level of abstraction.
Maybe we can template our way around it, but so far there has been no
pressing need to do so.
+
+Functors can be converted to `v8::InvocationCallback`s like:

{{{
struct MyFunctor {
Reply all
Reply to author
Forward
0 new messages