Hi,

In message "[ruby-talk:8037] String#unfreeze"
    on 00/12/24, ts <decoux / moulon.inra.fr> writes:

|>                                In addition, Ruby interpreter depends
|> on the fact that frozen objects, especially strings, are never be
|> unfrozen.
|
| This is because, rb_str_new4() and rb_str_dup_frozen() don't create a new
| object when the string is frozen ? Is this the only reason ?

Uh, maybe.  Some part of string copy-on-write system depends on the
fact that frozen strings would never be modified.  I'm not sure proper
copying on those two functions make unfreeze possible.  When I confirm
it, I would happily add Object#unfreeze to the future Ruby.

							matz.