From: Robert Dober Date: 2009-02-25T02:01:52+09:00 Subject: [ruby-core:22419] Re: [Patch 191p0 ] for ostruct freeze behavior I was about to file an error report. When I found this http://redmine.ruby-lang.org/repositories/diff/ruby-19?rev=22332 ? I wonder if I still shall add this error report, as the fix seems incomplete ( So would have my patch BTW. That is why I have backed up Jo�l's idea to forward freeze to @table or to a pseudo object in case one wants to keep table unfrozen for some unknown reasons ) require 'ostruct' class OpenStruct def frozen?; false end end o = OpenStruct::new( :a => 42 ) o.freeze o.a = 1 p o.a IOW it is fragile to rely on #frozen? JRuby's implementation is suffering from the same problem BTW. Robert -- There are some people who begin the Zoo at the beginning, called WAYIN, and walk as quickly as they can past every cage until they get to the one called WAYOUT, but the nicest people go straight to the animal they love the most, and stay there. ~ A.A. Milne (from Winnie-the-Pooh)