kotovalexarian-likes-github/ruby--ruby
1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
Code Releases Activity

Fix similar typos [ci skip]

Browse source 
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@56408 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
kazu 2016-10-12 15:28:07 +00:00
parent caa9083451
commit 7f887ab122
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/ChangeLog-1.8.0
View file

@ -21236,7 +21236,7 @@ Sun Jan 3 01:37:58 1999 Takao KAWAMURA <kawamura@ike.tottori-u.ac.jp>
Sat Jan 2 17:09:06 1999 Yukihiro Matsumoto <matz@netlab.co.jp> Sat Jan 2 17:09:06 1999 Yukihiro Matsumoto <matz@netlab.co.jp>
* eval.c (rb_jump_tag): new api to invoke JUMP_TAG. tag values * eval.c (rb_jump_tag): new api to invoke JUMP_TAG. tag values
can obtained from rb_eval_string_protect()/rb_load_protect(). can be obtained from rb_eval_string_protect()/rb_load_protect().
* eval.c (rb_rescue): now catches all exceptions but SystemExit. * eval.c (rb_rescue): now catches all exceptions but SystemExit.

2
doc/ChangeLog-2.1.0
View file

@ -2948,7 +2948,7 @@ Tue Nov 5 03:31:23 2013 Koichi Sasada <ko1@atdot.net>
Young objects will be promoted to old objects after one GC. Young objects will be promoted to old objects after one GC.
Old objects are not collect until major (full) GC. Old objects are not collect until major (full) GC.
The issue of this approach is some objects can promoted as old The issue of this approach is some objects can promote as old
objects accidentally and not freed until major GC. objects accidentally and not freed until major GC.
Major GC is not frequently so short-lived but accidentally becoming Major GC is not frequently so short-lived but accidentally becoming
old objects are not freed. old objects are not freed.