summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorYukihiro "Matz" Matsumoto <[email protected]>2014-06-01 02:51:24 +0900
committerYukihiro "Matz" Matsumoto <[email protected]>2014-06-01 02:51:24 +0900
commita22495df003cd0d9df729b7adb276a7f65b3fff7 (patch)
tree512fab59deb41ab7fafc2737bdeef44751eb1d30
parent35d4137da1cc82fc3a6ba2787d954c89740d661c (diff)
parentc86d7fe834370f32e686eec6a8c9ce0dfa739d04 (diff)
downloadmruby-a22495df003cd0d9df729b7adb276a7f65b3fff7.tar.gz
mruby-a22495df003cd0d9df729b7adb276a7f65b3fff7.zip
Merge branch 'master' of github.com:mruby/mruby
-rw-r--r--src/gc.c12
-rw-r--r--src/parse.y2
2 files changed, 7 insertions, 7 deletions
diff --git a/src/gc.c b/src/gc.c
index 4478b71f3..171f0858d 100644
--- a/src/gc.c
+++ b/src/gc.c
@@ -34,7 +34,7 @@
== Two White Types
- There're two white color types in a flip-flop fassion: White-A and White-B,
+ There're two white color types in a flip-flop fashion: White-A and White-B,
which respectively represent the Current White color (the newly allocated
objects in the current GC cycle) and the Sweep Target White color (the
dead objects to be swept).
@@ -43,8 +43,8 @@
that time, all the dead objects have been swept, while the newly created
objects in the current GC cycle which finally remains White are now
regarded as dead objects. Instead of traversing all the White-A objects and
- paint them as White-B, just switch the meaning of White-A and White-B would
- be much cheaper.
+ painting them as White-B, just switch the meaning of White-A and White-B as
+ this will be much cheaper.
As a result, the objects we sweep in the current GC cycle are always
left from the previous GC cycle. This allows us to sweep objects
@@ -73,8 +73,8 @@
mruby's GC offers an Generational Mode while re-using the tri-color GC
infrastructure. It will treat the Black objects as Old objects after each
- sweep phase, instead of paint them to White. The key idea are still same as
- the traditional generational GC:
+ sweep phase, instead of painting them White. The key ideas are still the same
+ as traditional generational GC:
* Minor GC - just traverse the Young objects (Gray objects) in the mark
phase, then only sweep the newly created objects, and leave
@@ -82,7 +82,7 @@
* Major GC - same as a full regular GC cycle.
- The difference to a "traditional" generational GC is, that the major GC
+ The difference from "traditional" generational GC is, that the major GC
in mruby is triggered incrementally in a tri-color manner.
diff --git a/src/parse.y b/src/parse.y
index c6795fb65..719e78218 100644
--- a/src/parse.y
+++ b/src/parse.y
@@ -5856,7 +5856,7 @@ mrb_parser_dump(mrb_state *mrb, node *tree, int offset)
{
node *n2 = tree->car;
- if (n2 && (n2->car || n2->cdr)) {
+ if (n2 && (n2->car || n2->cdr)) {
dump_prefix(offset+1);
printf("local variables:\n");
dump_prefix(offset+2);