@@ -755,7 +755,7 @@ Well, this could have been done, but there are good reasons why it was not. As
755755a matter of fact, this problem is deeply linked to the way `ruby` manages
756756objects.
757757
758- In `ruby`, memory used by for example string data (`char[]`) is directly
758+ For example, in `ruby`, memory used by string data (`char[]`) is directly
759759allocated using `malloc()`. However, the object structures are handled in a
760760particular way. `ruby` allocates them by clusters, and then distribute them
761761from these clusters. As at allocation time the diversity of types (and sizes)
@@ -776,11 +776,11 @@ useless. And beyond that, if `RString` had 4 pointers, `RObject` would use less
776776that half the size of the shared entity. As you would expect, it's wasteful.
777777
778778So the received merit for `iv_tbl` is more or less saving memory and speeding
779- up. Furthermore we do not know if it is used often or not. In the facts ,
779+ up. Furthermore we do not know if it is used often or not. In fact ,
780780`generic_iv_tbl` was not introduced before `ruby` 1.2, so it was not possible
781- to use instance variables in `String` or `Array` at this time. Nevertheless it
782- was not so much of a problem. Making large amounts of memory useless just for
783- such a functionality looks stupid.
781+ to use instance variables in `String` or `Array` at that time. Nevertheless, it
782+ was not much of a problem. Making large amounts of memory useless just for
783+ such functionality looks stupid.
784784
785785If you take all this into consideration, you can conclude that increasing the
786786size of object structures does not do any good.
0 commit comments