h8 0.1.2 → 0.1.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +2 -5
- data/hybrid8.gemspec +2 -2
- data/lib/h8/version.rb +1 -1
- metadata +5 -5
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 2ee6c0b2e2d9f2e6ee7c1baba1d2e5d5ff4bb82c
|
|
4
|
+
data.tar.gz: 1ce87dddfef9bc287f235c0bb31a69a03d32363c
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 511f1e2854ffccb6cb1d42b0ab7789bbd9173c31cf05a7d3fe24aba192d4fb2ad4dba6ba8039fc1b642312d2c138cbb8835bf47c2e36a1b3e736550771c470dd
|
|
7
|
+
data.tar.gz: 474499e5c938efd557c39de0383bbbc8d01b9b5a4eefe04fe86b66621b74de2edf6e41a6da96cdb551f083066f0fe355bebd0885d991ae9d6668320b59ec08b6
|
data/README.md
CHANGED
|
@@ -38,15 +38,12 @@ uncaught javascript exceptions raise ruby error in ruby code.
|
|
|
38
38
|
|
|
39
39
|
## Main difference from therubyracer/features not ready
|
|
40
40
|
|
|
41
|
-
- This version is not (yet?) thread safe*. For the sake of effectiveness, do not access same
|
|
42
|
-
H8::Context and its returned values from concurrent threads. Use Mutexes if need.
|
|
43
|
-
|
|
44
41
|
The pity thing is, if we will Lock() the context on each call to it, the performance degradation
|
|
45
42
|
will be notable and no matter whether you need threading with it. So, if you really need it, you
|
|
46
43
|
wrap it with Mutex or whatever you want, without slowing down all the rest of us.
|
|
47
44
|
|
|
48
|
-
-
|
|
49
|
-
perform on this core while javascript code runs).
|
|
45
|
+
- H8 is thread safe (users Lockers) but script is executed in the calling ruby thread without
|
|
46
|
+
releasing gvl (other ruby threads can not perform on this core while javascript code runs).
|
|
50
47
|
|
|
51
48
|
The same performance reason. If we release gvl on script start and reacquire it every time the ruby
|
|
52
49
|
object, callback, class, whatever is referenced from JS, the execution will considerably degrade. As
|
data/hybrid8.gemspec
CHANGED
|
@@ -32,7 +32,7 @@ spec = Gem::Specification.new do |spec|
|
|
|
32
32
|
spec.add_development_dependency "bundler", "~> 1.6"
|
|
33
33
|
spec.add_development_dependency "rake"
|
|
34
34
|
spec.add_development_dependency "rake-compiler"
|
|
35
|
-
spec.add_development_dependency "rspec", '
|
|
35
|
+
spec.add_development_dependency "rspec", '~> 3.1'
|
|
36
36
|
|
|
37
37
|
# spec.add_dependency 'libv8'
|
|
38
38
|
end
|
|
@@ -42,7 +42,7 @@ end
|
|
|
42
42
|
|
|
43
43
|
Rake::ExtensionTask.new "h8", spec do |ext|
|
|
44
44
|
ext.lib_dir = "lib/h8"
|
|
45
|
-
ext.source_pattern = "*.{c,cpp}"
|
|
45
|
+
ext.source_pattern = "*.{c,cpp,js}"
|
|
46
46
|
ext.gem_spec = spec
|
|
47
47
|
end
|
|
48
48
|
|
data/lib/h8/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: h8
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.1.
|
|
4
|
+
version: 0.1.3
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- sergeych
|
|
@@ -56,16 +56,16 @@ dependencies:
|
|
|
56
56
|
name: rspec
|
|
57
57
|
requirement: !ruby/object:Gem::Requirement
|
|
58
58
|
requirements:
|
|
59
|
-
- - "
|
|
59
|
+
- - "~>"
|
|
60
60
|
- !ruby/object:Gem::Version
|
|
61
|
-
version:
|
|
61
|
+
version: '3.1'
|
|
62
62
|
type: :development
|
|
63
63
|
prerelease: false
|
|
64
64
|
version_requirements: !ruby/object:Gem::Requirement
|
|
65
65
|
requirements:
|
|
66
|
-
- - "
|
|
66
|
+
- - "~>"
|
|
67
67
|
- !ruby/object:Gem::Version
|
|
68
|
-
version:
|
|
68
|
+
version: '3.1'
|
|
69
69
|
description: |2
|
|
70
70
|
Synergy of ruby and javascript code, almost completely integrates both languages, their
|
|
71
71
|
garbage collection models, object models and so on. Effective for tight ruby-javascript
|