Alan Burlison <Alan.Burlison@sun.com> writes: >> I think it had an effect if you applied it to the hash elements, but I >> don't think it ever did anything to the hash itself. > >Actually, that's wrong, setting a hash to readonly did affect its behaviour >even on 5.6.1, as the following test from the module test script checks: > ># Check readonly-ness of hash structure. >eval { $ks->{cpu_info}{$cpu}{$cpu_info} = {}; }; >print($@ =~ /^Modification of a read-only/i ? "ok $test\n" : "not ok $test\n"); > >So the reuse of the readonly bit to implement restricted hashes has indeed >broken existing working code. I'm now faced with having to have 2 versions >of the module :-( I _think_ that message is due to READONLY-ness of the _value_ > >-- >Alan BurlisonThread Previous | Thread Next